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

41–50 of 86 posts

Re: Why I'm using Next.js

#41

Post by chasd00 »

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

Typescript is a real pain, I’m still trying to figure out why it’s so popular. The constant nagging and extra typing (no pun intended) when using it vs regular JavaScript makes it a pain. Then, there’s the extra parsing step to change it back to JavaScript. Idk I don’t see the value yet.

Edit: I say “parsing step “ because that’s what it is. There’s no “compiling” and “transpile” is just a ridiculous way of saying parse and output.

Re: Why I'm using Next.js

#42

Post by ervine »

lucasmerlin wrote: post #15

We've been having a lot of problems with weird bugs with nextjs, so I can't really recommend it. Feels like it's a eternal beta. First, we've had a problem with nextjs not caching the response code for 404 pages, so 404 pages would have a 200 status code. Now they've fixed this they have a bug where they are caching the 304 response code, responding with 304 to every request and completely breaking the site. This has…

Yep their github management is atrocious. I understand it's a popular product so you get a lot of low quality issues opened, but there tons of real problems where no developer ever appears, and then are closed by the bot because of inactivity.

Infuriating. The longer I do this, the more that issue management responsiveness becomes a real consideration when choosing a dependency.

Re: Why I'm using Next.js

#43

Post by ushakov »

My last issue with Next was that when we were using SSR-mode with Server Components we couldn't change the env variables at runtime, unless the dev mode was enabled (otherwise it would just bundle them). We were deploying with Docker and needed for each deployment to have a different env variable. Sound like a simple task, until it's not

Re: Why I'm using Next.js

#45

Post by leerob »

ervine wrote: post #37
Tehnix wrote: post #29

Earlier quoted context omitted.

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…

Middleware works when self hosting. It's runtime is a subset of Node.js, since it's potentially running in front of every request in your application. We're still evaluating options here: https://github.com/vercel/next.js/discussions/46722#discussi...

Re: Why I'm using Next.js

#46

Post by ervine »

chasd00 wrote: post #41
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

Typescript is a real pain, I’m still trying to figure out why it’s so popular. The constant nagging and extra typing (no pun intended) when using it vs regular JavaScript makes it a pain. Then, there’s the extra parsing step to change it back to JavaScript. Idk I don’t see the value yet. Edit: I say “parsing step “ because that’s what it is. There’s no “compiling” and “transpile” is just a ridiculous way of saying pa…

Are you against typescript or types in general?

Re: Why I'm using Next.js

#47

Post by leerob »

ushakov wrote: post #43

My last issue with Next was that when we were using SSR-mode with Server Components we couldn't change the env variables at runtime, unless the dev mode was enabled (otherwise it would just bundle them). We were deploying with Docker and needed for each deployment to have a different env variable. Sound like a simple task, until it's not

This should be supported: https://github.com/vercel/next.js/discussions/44628#discussi...

Re: Why I'm using Next.js

#48

Post by conradludgate »

3c6bYDXLMj wrote: post #16
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…

Yep. Essentially a DevRel post.

To be completely fair, it's a response to someone who wrote about why to use Remix and not NextJS. The author of said post was apparently the CTO for Remix. Both sides are doing DevRel here

Re: Why I'm using Next.js

#49

Post by hu3 »

lwhi wrote: post #33
shmde wrote: post #32

Earlier quoted context omitted.

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.

[flagged]

It's good practice to introduce strong biases at the top of articles so readers can take that into consideration right away.

The article they are responding to did precisely that on their second paragraph:

> I’ve been using Remix since it was first released in 2020. I loved it so much I joined the team for 10 months to help get the community going and now I recommend and teach Remix on EpicWeb.dev. [1]

[1] https://www.epicweb.dev/why-i-wont-use-nextjs

Re: Why I'm using Next.js

#50

Post by chasd00 »

ushakov wrote: post #40

What are better options out there (for a Node developer) if you're not using Next.js? Going to rails isn't really an option I guess

I’ve been learning more of these stacks and found out about remix here in the nextjs release 14 thread. Remix seems pretty ok so far but I don’t have super strong feelings on nextjs either, it seems to work for me. I’m functioning as a system liaison at work for a team on nextjs which was my first exposure to it. That got my interest so I’ve been exploring front end frameworks lately. I would give remix a shot.
Post reply on HN