5 ms·
>which is exactly the opposite of how it used to feel when it first came out. I use React (actually Preact), but the old way, not with "use" anything, no hooks
by leptons 1y ago
>which is exactly the opposite of how it used to feel when it first came out.
I use React (actually Preact), but the old way, not with "use" anything, no hooks. It's pretty simple, but does a good job at what I need, and I'm doing pretty complex web applications with it.
There's no law saying you must use the bleeding edge of everything, the old React way is still plenty good for most things.
The way they rushed out hooks and everyone jumped on board was a red flag for me. I've used it, I've built stuff with hooks, but it's always seemed like fixing problems by creating more problems, and the hype around it was ridiculous.
- wredcoll 1y agoI feel the same way about vue switching to hooks. What is the exact problem we're solving?
- agos 1y agoHooks were introduced in early 2019, they're hardly bleeding edge
- leptons 1y agoI was not specifically talking about hooks being "bleeding edge" in 2025. I know when they were first released, and I don't need that techsplained to me. I'm speaking more generally about the trend of chasing "new, shiny" in front-end. Some people knee-jerk and just go for the "new, shiny" thing as soon as it happens. And other people still use the existing tech, because it's good enough.
- skydhash 1y agoI switch to hooks the moment they were in stable. Because functional components are simpler in nature. And the reactive apparatus that hooks are make it simpler to bring external modules. Writing HOC was a pain. Hooks are a good translation layer.
- bavell 1y agoApparently we are in the minority, but I find hooks great for DRY and composition. My components can be thin and presentational while the business logic is tucked away in neat little packages. Didn't realize how much I disliked class components and HOCs until hooks showed up. Footguns, learning curve? Sure, but I'll still make that trade.
- owebmaster 1y agoTreating one big function handling 10 different scenarios is not what I would call functional components, much less simpler in nature. React in its current incarnation is the best framework to create unmaintainable code.
- skydhash 1y ago> *Treating one big function handling 10 different scenarios is not what I would call functional components, much less simpler in nature. That’s an antipattern. Like the 200 lines function in imperative or the god class in OOP. Your components should be small and composable. Before directly using the standard hooks in the components, you should think first if it would not better to write a custom one. Scenarios should be handled by custom hooks and component should just get data from them. If you cannot test scenarios apart from your views and vice-versa, you’re doing it wrong