Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

You should know this before choosing Next.js

eduardoboucas.com

Post reply on HN
Print view View original

51–60 of 147 posts

Re: You should know this before choosing Next.js

#51

Post by taeric »

toddmorey wrote: post #33
taeric wrote: post #6

I was under the impression that Next.js was the successor to React? Is that not the case?

I could totally see how you'd arrive there. Backstory: create-react was a starter boilerplate for React built and maintained by Facebook. This was when webpack was the standard and just getting a local development environment to "hello world" for React could be challenging.[1] That project was depreciated and the popularity of the Next.js site framework for react projects (plus I certainly assume heavy lobbying from…

Yeah, this is what I was remembering. Glad to see I didn't flat out hallucinate the idea that "create-next" as the starting spot for creating a React site.

Re: You should know this before choosing Next.js

#52

Post by jFriedensreich »

I was always highly sceptical of vercel even though or maybe also because i really love the design and public appeal they are going for. But something about everything they do and talk about gives me the creeps, something is telling me that they are not genuine and keeping something. Its maybe the same feeling when you talk to a really pleasant to talk to person who you just know is a psychopath making the heir on your neck stand up.

This was probably at the strongest when they could not decide on the edge function strategy and made a handful of statements that made no sense or made partial sense but were very clearly not the full picture.

Buying rich harris while assuring this would have no impact on the level of sveltekit lock-in crossed a line for me to feel really anxious. So far i did not see anything concrete go bad with sveltekit but its hard to imagine a scenario where this would not happen. Lets hope rich can keep his integrity and awareness enough to walk away at the right time.

Re: You should know this before choosing Next.js

#53

Post by matt-p »

rco8786 wrote: post #12

I was using next.js when they switched from the pages router to app router. I ended up just abandoning the project, the app router experience was that bad, and haven't really been keen on picking up next.js since then. It's always seemed clear that Vercel has been, at best, OSS- ish . Trying to play both sides of claiming to be open source but also (somewhat sneakily) building a walled garden to lock users into their…

To this day I still use pages only. Long term or for a new project I guess I'll have to look into astro or vite/express

Re: You should know this before choosing Next.js

#54

Post by joshdavham »

I feel that open source is truly at its best when it’s done by enthusiasts/hobbyists and not necessarily by corporations. React and Nextjs always smelled a bit suspicious to me whereas Svelte and Vue did not.

There’s actually an old PG essay talking about Java where I feel a lot of what he says applies to Nextjs: https://www.paulgraham.com/javacover.html

Re: You should know this before choosing Next.js

#55

Post by nonethewiser »

tmpz22 wrote: post #42
diggan wrote: post #24

Earlier quoted context omitted.

> next.js when they switched from the pages router to app router It is react-router all over again. For those who weren't around, react-router appeared early in React's life, and lots of people were using it. But, for every major version they released, they completely changed the way of doing the routes/routing, so if you wanted to use a maintained release, you'd have to constantly refactor, often without any real ga…

React-router can still cause weird build issues to this day, particularly with LLM generated code that cannot understand version compatibilities.

An emergent benefit of stability

Re: You should know this before choosing Next.js

#57

Post by vmg12 »

sama004 wrote: post #48
vmg12 wrote: post #14

The single reason I switched from next.js was because it was taking me 6-7 seconds on a small project to see changes I made appear in the browser during development (on an M1 Max Macbook pro with 64gb of ram). This is when using the app router, where every change requires a compilation step. I now just use a React SPA with Vite.

what do you use for routing?

Tanstack router

Re: You should know this before choosing Next.js

#59

Post by debacle »

nonethewiser wrote: post #50
debacle wrote: post #46

Earlier quoted context omitted.

I disagree with this a little bit. Yes, a lot of the react-router changes are a PITA especially since some of the breaking changes are non-obvious. But most of the changes have been syntactical, and seemingly logical. A bigger gripe with react is that everything is so interdependent that things like react-dom and react-router might as well just be part of react - if you update one, you need to update the other anyway…

> Yes, a lot of the react-router changes are a PITA especially since some of the breaking changes are non-obvious. But most of the changes have been syntactical, and seemingly logical. "Syntactical" seems to reinforce his point, no? As opposed to functional.

The intent I think is "Lets refactor the syntax of the router so we can add more functionality without creating a boondoggle." At least from what I have seen.

Re: You should know this before choosing Next.js

#60

Post by oxidant »

amadeuspagel wrote: post #22

> With Next.js having such a sizeable share of the market, I would expect a lot more hosting options, which would foster competition and innovation across the board, ultimately benefitting users and the web. Would it? Or would it turn Next.js hosting into a commodity with zero marginal profit, ulimately making it impossible to fund development?

WordPress, despite all of the current drama, is an example of an open source project with many different competitors and development seems to move just fine.

Creating an artificial moat and misrepresenting capabilities, as outlined in the article, may bring value to Vercel, but it can hurt consumer confidence. I would not and have not chosen Next for projects because of the lock in.

Post reply on HN