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

Why I'm using Next.js

leerob.io

Post reply on HN
Print view View original

31–40 of 86 posts

Re: Why I'm using Next.js

#31

Post by poisonborz »

Tehnix wrote: post #29
the_mitsuhiko wrote: post #18

Earlier quoted context omitted.

Next’s support outside of Vercel is best effort it seems. Which is fine as Vercel funds it, but it feels like there is a conflict of interest. There is after all a reason for OpenNext’s existence.

I really don’t understand this sentiment, it is extremely easy to build and deploy Next.js yourself?? You either: - Build static files and host it like any other framework (e.g. throw it in an S3 bucket)[0] - Or, run a Node.js server Where’s the Vercel exclusive part there? [0] Here’s me doing exactly that, going through the same steps I would for literally any Frontend framework, including the WASM alternative I als…

Well that's the problem, you will not see the glass wall until too late. For my case, that you can add API middleware, but you can't run any "not edge compatible" code because of Vercel reasons.

Re: Why I'm using Next.js

#32

Post by shmde »

lwhi wrote: post #14
robertjpayne wrote: post #13

> If you're new here, I'm Lee. I work on Next.js. I've also made some courses about using Next.js before I joined Vercel. This alone should be further up the post…

Why?

What why ? The term that you work for Vercel should be at the top so that people realise this isnt a neutral 3rd party but a company paid spokesperson.

Re: Why I'm using Next.js

#35

Post by mplewis »

lovetocode wrote: post #34

Is anyone just using vanilla React with no TypeScript or Framework of any kind? I’ve tried Remix and Next js and just find them so cumbersome. Typescript causes me more headaches

After using TypeScript, I’m never going back to vanilla JavaScript if I can help it.

Re: Why I'm using Next.js

#37

Post by ervine »

Tehnix wrote: post #29
the_mitsuhiko wrote: post #18

Earlier quoted context omitted.

Next’s support outside of Vercel is best effort it seems. Which is fine as Vercel funds it, but it feels like there is a conflict of interest. There is after all a reason for OpenNext’s existence.

I really don’t understand this sentiment, it is extremely easy to build and deploy Next.js yourself?? You either: - Build static files and host it like any other framework (e.g. throw it in an S3 bucket)[0] - Or, run a Node.js server Where’s the Vercel exclusive part there? [0] Here’s me doing exactly that, going through the same steps I would for literally any Frontend framework, including the WASM alternative I als…

It's easy but there are decisions made that hamstring you - like being unable to change cache-control headers in the next.config.js or middleware or have your middleware use node APIs, which is especially stupid because when self-hosting... it's running in node!

They are optimizing for deploying to the edge, which when self hosting you don't need to.

So whether malicious or not, their guard rails conveniently make it frustrating to self host once you need to do anything outside of their garden.

Re: Why I'm using Next.js

#38

Post by chasd00 »

lucasmerlin wrote: post #22
lwhi wrote: post #19

Earlier quoted context omitted.

This is my big problem with proprietary software; and why open source pragmatically makes more sense. Fixing bugs is down to priority and incentives of the parent company.

I mean it is open source and someone even made a PR to fix the bug in question and I guess I could use their fork until it's fixed.

I was about to say, just fox the bug submit a pull request and use your fork until it’s merged. Isn’t that the point of all these fancy source control tools?

Re: Why I'm using Next.js

#39

Post by lloydatkinson »

I can’t recommend Next after using it even on a small project.

Whatever it sends to the browser is enough to eventually freeze the entire browser tab if you have the dev tools open. This was a daily recurrence.

Also, the “fix” for many issues was to throw “use client” at the top of problem files. Serving the application whether first time load or dev time with hot module reload took an age.

Really quite a miserable experience honestly. I have much better experiences with either a plain SPA or Astro.

Post reply on HN