←back to thread

Next.js is infuriating

(blog.meca.sh)
1033 points Bogdanp | 1 comments | 02 Sep 25 06:57 UTC | HN request time: 0.246s | source
Show context
dev_l1x_be ◴[02 Sep 25 13:03 UTC] No.45102589[source]▶
> In general Next.js has so many layers of abstraction that 99.9999% of projects don't need.

This true to most software projects that are used more than one set of people. Joe Armstrong proposed a solution that we should opensource functions only and people could assemble everything else using these opensource functions. I start to think that he might be right and instead using "frameworks" we should use these set of functions instead.

replies(4): >>45102626 #>>45102823 #>>45102962 #>>45107791 #
1. snisarenko ◴[02 Sep 25 13:07 UTC] No.45102626[source]▶
Spot on. This is the core problem.

The ammount of functionality is not the problem.

The problem is that the functionality is not a set of composable functions and classes. It's an inversion of control "framworky" blackbox, where behavior is hard to reason about.