←back to thread

Next.js is infuriating

(blog.meca.sh)
1033 points Bogdanp | 2 comments | 02 Sep 25 06:57 UTC | HN request time: 0.408s | source
Show context
usernamed7 ◴[02 Sep 25 08:39 UTC] No.45100493[source]▶
as a Rails dev this makes me LOL. I would have expected the rube goldburg machine of JS frameworks to be more robust and ergonomic by now, but it looks more to be hacks built on top of hacks with no real vision or technical leadership.
replies(3): >>45100508 #>>45100526 #>>45100761 #
b_e_n_t_o_n ◴[02 Sep 25 08:42 UTC] No.45100508[source]▶
Like said in the article, most other JS frameworks are actually pretty good these days.
replies(1): >>45100557 #
zwnow ◴[02 Sep 25 08:50 UTC] No.45100557[source]▶
I work with Vue 2 and Vue 3, both options and composition APIs and both are pretty great. I dont know how it's like for very complex UI but it 100% fulfills my needs.

Also shout out to Pinia, I love you!

replies(1): >>45100901 #
sensanaty ◴[02 Sep 25 09:49 UTC] No.45100901[source]▶
I have a monstrosity of a Vue 3 project at work and I far prefer it to any "elegant" React codebase I've ever had the displeasure of working with. Boggles the mind that React still has any mindshare to me, Vue and Svelte are both superior to it in pretty much every way except for availability of component libraries (which isn't so relevant in my line of work), and a slight edge in terms of TypeScript support (mostly a problem with Vue's props).
replies(3): >>45100953 #>>45101576 #>>45101642 #
sfn42 ◴[02 Sep 25 11:24 UTC] No.45101576[source]▶
I think React is fine, the problem is that every single react app I've inherited is ass - people just do everything incorrectly and overcomplicate simple things. Components with like 5 different useEffects, huge global state causing all kinds of bugs, way too much frontend logic in general. The amount of JS code that exists just to mimic things you can do with HTML and CSS is staggering.

Everyone complains that react is so slow and horrible, it isn't. It's their code that's slow and horrible, react is snappy as hell when you use it properly.

replies(2): >>45101805 #>>45101993 #
zwnow ◴[02 Sep 25 11:46 UTC] No.45101805[source]▶
> Everyone complains that react is so slow and horrible, it isn't. It's their code that's slow and horrible, react is snappy as hell when you use it properly.

Why use something that you have to use "properly" when there are things out there that enforce being used properly?

replies(1): >>45102230 #
1. sfn42 ◴[02 Sep 25 12:30 UTC] No.45102230[source]▶
Because I'm not convinced there exists a programming language/library/framework that you can't use improperly.

And just to be clear I'm not saying react is better than Vue. I don't know Vue. Maybe it is better. All I'm saying is react is alright in my experience, the problem is people overcomplicate and mess things up. I've seen that in pretty much every piece of software I've ever worked on, backend/frontend/whatever. So the claim that Vue just magically can't be messed up is difficult for me to believe.

replies(1): >>45102939 #
2. zwnow ◴[02 Sep 25 13:37 UTC] No.45102939[source]▶
I can understand that. For me personally, Vue has a limited set of lifecycle hooks you can use so its hard to pick the wrong one. React on the other hand gives u some kind of use_ for everything, so its first and foremost harder to understand the app lifecycle and to pick the correct hook.

With Vue I started to use Pinia for my whole apps state management, which are data stores. Clean and centralized logic, with React idk what a substitute would be.

I know React can be clean too, but that (in my opinion) requires a lot more depth of knowledge about the framework.