21–30 of 50 posts
Earlier quoted context omitted.
[flagged]
React was ruined from the moment they abandoned class components and introduced hooks. Vercel is just continuing the trend of hype against common sense.
I'm still yet to be convinced React Server Components are anything but a disaster to the developer experience. Mixing backend and frontend without a clear boundary is terrible for any codebase beyond a handful of contributors.
(The conclusion could, of course, also be that it's just not feasible to create that kind of user experience. Luckily, traditional patterns still work just as well.)
I'm still yet to be convinced React Server Components are anything but a disaster to the developer experience. Mixing backend and frontend without a clear boundary is terrible for any codebase beyond a handful of contributors.
The prime motivator for it is a certain user experience. I'm not sure they've found the best developer experience for providing that user experience, but I'm also not sure that a better DX is possible - the whole concept has quite a bit of inherent complexity, I'm afraid. (The conclusion could, of course, also be that it's just not feasible to create that kind of user experience. Luckily, traditional patterns still w…
Earlier quoted context omitted.
I just don't understand this take, every time I hear it I wonder if people just haven't spent the time to adjust their mental model. Hooks are IMO the best thing that happened to react.
I have spent more time than I wished for on React debugging tools, and useXXXX spaghetti calls.
Earlier quoted context omitted.
React was ruined from the moment they abandoned class components and introduced hooks. Vercel is just continuing the trend of hype against common sense.
Spot on, incredible how OOP hate can mess up a framework. Vercel, the only thing they have going for the app model mess, are the partnerships with SaaS vendors that make them the must go tooling. However this will eventually come to an end.
Earlier quoted context omitted.
I have spent more time than I wished for on React debugging tools, and useXXXX spaghetti calls.
You can write spaghetti with class components, too. Doesn't sound like a hooks issue to me.
Earlier quoted context omitted.
Spot on, incredible how OOP hate can mess up a framework. Vercel, the only thing they have going for the app model mess, are the partnerships with SaaS vendors that make them the must go tooling. However this will eventually come to an end.
It wasn't OOP hate, it was hatred of splitting functionality across a number of methods rather than putting it in a single (reusable, sharable!) hook and having your component consume it.
I only touch React now, because of SaaS partnerships with Vercel.
Otherwise I pretend it doesn't even exist.
It happens to all of us. However, I think it’s much easier nowadays with LLMs for something productive like this to come out of it. I can notice something wrong and triage or even fix it before the point where I’d normally start to feel the subconscious pull of opportunity cost telling me to stop.