and it's not compatible with latest version of react?
> React 19 Memory Optimization Detected
React has detected that this is a large page and is removing source information that is necessary for JSX Tool to run. This optimization helps improve performance but prevents JSX Tool from inspecting your React components. You can either navigate to a different page or override this limitation using the proxy setup.
It is. You need to setup the dev server to overcome this limit. That’s why we put that warning there. React 19 limits the number of fiber nodes with source maps to 10k. When you enable the proxy we update it to 1m but we have to do a find replace in the source for this limit, so you have to proxy through us or let our vite plugin transform the js file.
I would imagine it has more to do with its principal function in recycling ADP back to ATP (fuel for cells). People who are sleep deprived also have impaired glucose metabolism, meaning that the cellular "fuel pipeline" is impeded. Perhaps creatine is especially helpful under these conditions.
Hypothetically, more water retention would mean that the fluid being flushed is less concentrated, and if the flushing mechanism is triggered by a certain concentration level then it'll happen less frequently.
Hard to imagine that it would be worth more than a few percent though.
I think it was great at first when llms were new and prompting required more strategy. Now the amount of of abstractions/ bloat they have for essentially string wrappers makes no sense
"In my experience, every artistic project hits a 'valley of despair' about half way through. It's that moment where your imagination gets ahead of your ability and failure seems inevitable. However, it's in that valley where creativity thrives because it takes out-of-the-box thinking (or a switch of toolboxes) to climb out.
Creative success isn't always about sticking to the plan. It more often than not looks like finding alternate solutions and being flexible in the face of challenges."
Are there any plans to help writers with discovery? It seems the only way to to build an audience is to already have an audience of some sort. This is one of the things that I like about Medium. They will recommend articles based on interests and have great SEO.
Definitely. The current Discover tab in the app is admittedly pretty basic - just search, the same featured publications from the homepage on substack.com, and categories. We have a lot of ideas for how to improve this tab, as well as other discover mechanisms throughout the app.
One area I'm especially excited about: discovery through the lens of the writers you trust. What are those writers reading themselves? What else are their readers (whose taste you ostensibly share) reading? We have a light version of this already with reader profiles in the app (and on web) - when you subscribe to a publication, you can choose whether to display it on your profile. Lots more we could do though.
Discoverability based on more specific categories, like "humor/comedy" "movies" "advice" would be more helpful than trying to triangulate between what a writer/author reads and what a new reader is reading. Writers who are more open-minded subscribe to newsletters that have nothing to do with the content they write about. If a reader is interested in more "humor" writing, for example, it doesn't make any sense to suggest a travel newsletter simply because the author of the article they are looking at reads it, and you are deeming it higher quality because of that when it may not really be better than other newsletters in the same category but rather a reflection of a personal relationship the author has with another author. To a lesser extent the same goes for the readers of a publication. People have eclectic tastes and are not monolithic. But as a reader if I'm enjoying an article under the category "movies" then I would appreciate seeing articles that are tagged with related terms like "film" "cinema" "movie recommendations" "movie reviews." The lack of tagging or more nuance in the categories Substack offers really limits discoverability.
> React 19 Memory Optimization Detected React has detected that this is a large page and is removing source information that is necessary for JSX Tool to run. This optimization helps improve performance but prevents JSX Tool from inspecting your React components. You can either navigate to a different page or override this limitation using the proxy setup.