Next.js is infuriating

(blog.meca.sh)

1033 points Bogdanp | 2 comments | 02 Sep 25 06:57 UTC | HN request time: 0.634s | source

Show context

coxmi ◴[02 Sep 25 09:25 UTC] No.45100774[source]▶

Deno Fresh seems like it has the right approach. It’s not complicated, the docs are refreshingly simple, and it handles both server and client logic without getting confused.

It’s just a shame it’s Deno-only (although I completely understand why)

replies(4): >>45101637 #>>45102185 #>>45102475 #>>45102854 #

1. robertjpayne ◴[02 Sep 25 12:25 UTC] No.45102185[source]▶

>>45100774 #

I feel like Fresh being Deno only isn't the primary issue. It's based on Preact which is really just a non-starter for so many because it isolates away too much of the react ecosystem instantly.

replies(1): >>45102341 #

2. coxmi ◴[02 Sep 25 12:40 UTC] No.45102341[source]▶

>>45102185 (TP) #

I don’t disagree on that front, the React ecosystem is huge, and rebuilding a load of complex components is often beyond the budgets of many greenfield projects.

I also don’t believe a React monoculture is good, so a growing Preact or Solid ecosystem would be really positive, alongside growing web/DOM standards to ultimately make these frameworks more of a light wrapper around some trivial updates.

React and Next.js, to me, have done the typical architecture astronaut thing, and it feels like they’ve both increased the barrier to entry and just made everything a little more complicated than it really needs to be for much of the web.

↑