←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.488s | source
Show context
pjmlp ◴[02 Sep 25 08:25 UTC] No.45100415[source]▶
I don't get these kind of complaints, coming from Java and .NET web frameworks, Next,js is the only sane frontend framework followed by Angular.

Saying this as someone doing Web related development since 1998, glory days of Perl and CGIs.

replies(3): >>45100468 #>>45100541 #>>45101200 #
bob1029 ◴[02 Sep 25 08:47 UTC] No.45100541[source]▶
Angular is absolutely not a sane framework. I'd argue it used to be, but you can't build trust in anything after being rugpulled with 4+ major breaking refactors over the years. If you get it that wrong that many times, I start to wonder what the actual purpose of the framework is.
replies(5): >>45100665 #>>45100727 #>>45100823 #>>45101025 #>>45103219 #
1. pjmlp ◴[02 Sep 25 09:17 UTC] No.45100727[source]▶
In consulting we don't do upgrades, we come, we deliver, and we leave, with maintenance contracts for existing deployed versions.

For an upgrade someone has to pay for it anyway, so whatever pains there are, they are reflected on project budget anyway.

More devs should do the math of work hours to money.

replies(1): >>45103031 #
2. icedchai ◴[02 Sep 25 13:44 UTC] No.45103031[source]▶
This really highlights one of the main differences between "product" and "project" centric work. With a project, it's the client's problem ($$$.) Usually they'll balk at the dollars and effort required and accept the risks. Even with an outdated, obsolete framework, the actual risks are often minimal. "It's still working, right?"