91–100 of 135 posts
I think those people would be better served by frameworks that hold fine grained reactivity as a virtue. If you have appetite for spaghetti at least use real pasta instead of trying to roll steak into thin stripes to tangle it.
Nextjs is pushing for the server components and I don't really blame them for doing so. Netlify is trying to back anything that's not nextjs. If anything I'm kind of surprised that big cloud players are completely ignoring this market right now.
The more I get into RSC I have the feeling their main purpose is to pump up Vercel bills. A reason to buy more of their expensive compute resources. They are nice in theory, but I don't see that many benefits over simple SSR, or the more traditional concept of server generated HTML with interactive islands. Next.js applications often feel way less responsive than SPAs with proper pre-rendering on first load.
React is darn good. Don’t mess with it and go into enshittificaion.
Earlier quoted context omitted.
> they always devolve into these blobs of non-deterministic async state with unpredictable performance Exact same experience here. I've been banging this drum for years. When hooks came around I thought they might make it better, but alas, we are still in a downwards spiral. Building web apps is 10x more complicated today than it was ten years ago, with nothing to show for it. I'm happy to see some known voices in th…
Building web apps with React is just much faster than doing it without, even when using Angular complex apps will always be complex. You can’t have an easy solution when you have tons of interaction and state.
Desktop software was never this fragile.
Earlier quoted context omitted.
I disagree that they were magic - you could build a test renderer for yourself and see pretty easily how they'd work. The system as a whole was understandable, and it fit into an existing mental model: you implement this interface, and React will call your methods. The specifics of how and when it did were part of the system on the other side of the interface. Hooks on the other hand are functions that you call, whic…
Hooks are not like functions. They are like imports. They provide your component with piece of functionality. You don't put imports in if-s or for-s. It's as simple as that.
There’s not necessarily bad reasons for this, but the cognitive overhead of this is relatively high compared to existing language functionality.
Alongside the work on server components, they also deprecated Create React App, which was previously the official way to create new apps for development, and which had pretty good ergonomics. However, you won't find that documented on the actual CRA site - when you go looking for why your dependencies are out of date, you'll find references in obscure GitHub issues: https://github.com/reactjs/react.dev/pull/5487#issu…
Vite is the new unofficial CRA. Superior in nearly every aspect.
Like the original article, I’m just kind of annoyed at React about this. There’s probably great reasons to change (albeit, I don’t really think even that comment communicates them well), but it’s annoying.
Earlier quoted context omitted.
Per the blog post announcing it, it's not recommended that you use that hook directly, only in libraries: > useSyncExternalStore is intended to be used by libraries, not application code. https://react.dev/blog/2022/03/29/react-v18#usesyncexternals...
I know. So either use an existing library or build your own. But don't useEffect instead.
Earlier quoted context omitted.
Building web apps with React is just much faster than doing it without, even when using Angular complex apps will always be complex. You can’t have an easy solution when you have tons of interaction and state.
> You can’t have an easy solution when you have tons of interaction and state. Desktop software was never this fragile.
It is ridiculous to suggest that React is worse today than ten years ago. Remember all that time people spent battling their build scripts? Or what about the obtuse 3rd-party state management libraries everyone used to augment class components? It was torturous from the start.
Earlier quoted context omitted.
Building web apps with React is just much faster than doing it without, even when using Angular complex apps will always be complex. You can’t have an easy solution when you have tons of interaction and state.
I started a new React project back in December after being annoyed with Angular, just to see whether it would be any less annoying and/or quicker. It's been neither of those things and I'm actually beginning to regret making that choice.