If the hook's timeline holds true for data loading, we have about 5 years.
Thank you to the react team for working on this hard problem and giving it to me for free. Remember there are 2 types of libraries out there: the ones people complain about and the ones no one uses.
</Rant>
The original set of hooks were finally perfected last year with react 19.2. Some of the missing items were adding useEffectEvent fixing a major issue with useEffects, ref functions with clean up fun, and React Compiler helping with state and context, and that took about 7 years.
4/5
I should be able to write code like in the and it works, but I get an infinite loop.
playground.react.dev#N4Igzg9grgTg...
If you don't write your code to cover these foot guns your app will fail in epic ways. React's model is good. It takes a while to perfect it.
3/5
3) The loading boundary needs to be outside the component, making it harder to port code to this model
4) you need an error boundary that is a legacy class component
React is so close to greatness that it is frustrating. There are good reasons for all these items, but it is still annoying
2/5
<rant>
What you are showing is very close to the perfect API, but the React implementation of it has so many little foot guns that make it harder than it should to use:
1) the fetching promise needs to be stable or cached.
2)Suspense does not persist state between loading to complete
1/5
I love TanStack Query, but data-loading primitives should be built into the UI library/framework, not third-party libraries. If I am doing a simple job of calling an API, then I should not have a lot of boilerplate or need a third-party library
SolidJS basically does what I want with createResource. React + React compiler + use is so close to perfection if this worked, but promises must be cached for use
playground.react.dev#N4Igzg9grgTg...
I dream of a React version, where fetching data with use is easier than using useEffect.
Good luck, you are a hero for getting that far
Congratulations to @seth.blue
A parady O'Reilly book cover with a pencil illustration of a horse as the main detail. The title is "Moving Fast and Breaking Things, Fragile Development Guide" At the top, text reads "Just put the technical debt on my credit card"
I generated this nearly 10 years ago in 2017 and it feels even more relevant now lol
Congratulations, I am surprised Thought Works would choose Svelte because Svelte files come before test files a clear TDD violation... Just showing how great svelte is!
It is called your salary, but the prep training is not of sufficient quality.
The close source shut-in strikes again :(
I want to keep my zero user developer status so I cannot ship, but be thankful I am too cheap to buy domains.
@vuejsamsterdam.bsky.social, thank you for posting your conference videos on YouTube one at a time.
Another great article by @tkdodo.eu.
If you are reading this, you have time to read it now.
When you have to use webpack in 2026
This is very cool
If I were doing a phishing attack, the email would be about security training.
Yeah, Claude is such an annoying coworker.
Sorry I cannot give you that source because it is my company code
github.com/MaxwellCohen...
github.com/MaxwellCohen...
github.com/MaxwellCohen...
Are 3 rsc personal projects I have
Great article by @chriscoyier.net on all the great features in and coming to js in 2026
frontendmasters.com/blog/what-to...
This is one of the most useful threads on using AI in 2026. I used this process to solve 3 bugs yesterday at work across 3 repos where I have mid-level expertise.
A software package page for "js-yaml" on npm shows details like version, license, download stats, and a warning about dependency necessity.
This @npmx.dev feature that suggests a faster, more performant alternative is seriously good 🚀
2 years ago, @sebmarkbage.calyptus.eu merged a PR removing the best variable name in React __SECRET_INTERNALS_DO_NOT_USE_OR_YOU_WILL_BE_FIRED for the much less scary _INTERNALS_DO_NOT_USE_OR_WARN_USERS_THEY_CANNOT_UPGRADE
Making the jobs of React developers much safer.
github.com/facebook/rea...
I blame the recent React CVEs on removing React.__SECRET_INTERNALS_DO_NOT_USE_OR_YOU_WILL_BE_FIRED. AI and humans now think that they can modify React internals without consequences
- personal projects I am a big fan of Composer 2 in Cursor
- work gpt 5.4 in Copilot
Can I have your permission to use the Vercel free tier for commercial purposes?
/s