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

141–147 of 147 posts

Re: You should know this before choosing Next.js

#141

Post by littlecranky67 »

9rx wrote: post #140
littlecranky67 wrote: post #139

Earlier quoted context omitted.

> But, man, at that point you're bringing a bulldozer (with a super uncomfortable operator's station!) to drive a nail. I think I do exactly the opposite. Having no SSR but everything be statically exported allows me to get away with cheaper hosting on the backend side (the REST API is on a cheap VPS). Static exported SPA means, the user's browser does all the heavy rendering. Plus, no AI bots or search engines contr…

> Having no SSR but everything be statically exported allows me to get away with cheaper hosting on the backend side Building a static website is very reasonable. Using the monstrosity that is Next.js to build a static website seems like super overkill, and I am not sure it offers a good developer experience to justify it[1]. [1] My experience with it had a need for dynamically driven pages, so it may just be that it…

You confuse a static website with a statically exported webapp. The site I do and posted a link to has a user/login section with lots of interactivity. Plus, there are features like using the webcam for scan QR codes (using a wasm library to read QRcode in JS from a media stream), receiving push notifications (and be a PWA on iOS), generating customizable print cards, etc.

Re: You should know this before choosing Next.js

#142

Post by braebo »

buffalobuffalo wrote: post #84
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…

I think the fundamental problem is that next.js is trying to do two things at once. It wants to a) Be fast to load for content that is sensitive to load speeds (SEO content, landing pages, social media sharable content, etc). It also wants to support complex client side logic (single page app, navigation, state store, etc). Doing those two things at the same time is really hard. It is also, in my experience, complete…

Sveltekit excels at this out of the box. And it’s simpler/easier than vanilla, let alone anything React-based.

Re: You should know this before choosing Next.js

#143

Post by wirybeige »

akvadrako wrote: post #124
wirybeige wrote: post #78

Earlier quoted context omitted.

It's acceptable for me because I (and others on my team) do not have to way 6-7 seconds almost ever, it is nearly instant. On odd occasion changes can take a long time to show up, ~5 seconds, but it seems restarting the server fixes it, so not sure what that is about.

Do you use it on vercel, maybe? I had the same experience of slow refreshes on the NextJS project I worked on (running locally) and the other seasoned NextJS developers didn't think it was unusual.

We do not use vercel. Unfortunate that the experience varies so much.

Re: You should know this before choosing Next.js

#144

Post by mdhb »

9rx wrote: post #128
mdhb wrote: post #125

Earlier quoted context omitted.

I think it’s literally the other way around. The CTOs previous role was in charge of Google’s search experience.

> I think it’s literally the other way around. Aside from the "appeal to authority", what suggests to you that they are strong in engineering? > The CTOs previous role was in charge of Google’s search experience. Google search also having decent product vision, but poor engineering execution, sounds about right. I don't know how many times I've heard people say they want to use Google search but have to resort to sil…

This is truly peak HN.

Yes, this multi billion dollar revenue stream is “one text input box and two buttons”.

Truly amazing insights.

Re: You should know this before choosing Next.js

#145

Post by matt-p »

derkoe wrote: post #109
matt-p wrote: post #53

Earlier quoted context omitted.

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

I guess Tanstack Start is also a very good alternative to check out https://tanstack.com/start/latest

Looks like a pretty good option thank you

Re: You should know this before choosing Next.js

#146

Post by matt-p »

floydnoel wrote: post #130
matt-p wrote: post #53

Earlier quoted context omitted.

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

i use Vite and built my own router. Works great and i can do a whole SPA with just that.

Me too, but it's actually really nice ergonomics to have the backend in the same 'codebase' for small projects. Of course this can all be done manually, but the last thing I want to be doing when starting a three day project is spending the first morning/day doing boilerplate stuff.
Post reply on HN