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

Next.js 14

nextjs.org

Post reply on HN
Print view View original

11–20 of 157 posts

Re: Next.js 14

#11

Post by pjmlp »

joduplessis wrote: post #6

The general direction React (+ Next) is going worries me a bit at times. I might be too conservative, but I want my JS on the frontend and not hot loaded from the server. For this reason I'm much more excited about Vite/Bun/Dino/etc. Also thank god for shit like Preact.

What worries me are the partner agreements Vercel is making with several enterprise products, making Next.js the only official frontend stack for their products.

With everything else being DIY integration, and lesser tooling.

Re: Next.js 14

#12

Post by joduplessis »

pjmlp wrote: post #11
joduplessis wrote: post #6

The general direction React (+ Next) is going worries me a bit at times. I might be too conservative, but I want my JS on the frontend and not hot loaded from the server. For this reason I'm much more excited about Vite/Bun/Dino/etc. Also thank god for shit like Preact.

What worries me are the partner agreements Vercel is making with several enterprise products, making Next.js the only official frontend stack for their products. With everything else being DIY integration, and lesser tooling.

I think for me the saving grace is the pervasiveness of the React paradigm. Porting code from React to Preact (obvs), Vue3, Stencil or Solid is easy peasy because the patterns are the same. And thanks god for that.

EDIT: Honestly a web components framework with 1-to-1 likeness in API would be first class. I'd jump immediately.

Re: Next.js 14

#13

Post by ldjkfkdsjnv »

lgkk wrote: post #4

How does this offering (and other serverless postgres) do when there is a ton of data and read/write happening? In my case the most data I've dealt with had a few tens of billions of records. I haven't really worked on small-ish scale things until starting to work on my startup. I've always depended on managed postgres, and I use Go for all my services. I don't really have any experience using things like Vercel that…

I just made basically the same comment, I'm pessimistic, but open minded. Hoping someone can drop some insight on this thread

Re: Next.js 14

#14

Post by samschooler »

Anyone using Next.js in production? Can you speak to the resources needed or optimizations to reduce said resources? I'm worried with how much lifting the server does that, it could rack up a pretty hefty AWS bill if I'm not careful.

Re: Next.js 14

#15

Post by boredtofears »

thinkingkong wrote: post #10

It's hard to take Vercel at face value these days with all of these improvements and announcements. Are we supposed to - in hindsight - understand that odd version numbers of their codebase were really just unstable releases all along? The app server implementation wasn't really meant to be used because it was an experimental release? I'm having a difficult time not being salty about this entire situation. There are…

I stopped paying attention when someone recently told me that everyone uses nextjs because “nextjs is meta right now”. Mind you this person has been a developer for about 3 years (not that there’s anything wrong with that but it gives you an idea of whose buying into this stuff)

Vercels devrel is by far the best thing that they do, miles ahead of their engineering.

Re: Next.js 14

#18

Post by orf »

Fuck next.js. Honestly. Check out how it bundles and sends the entire react-dom library twice to every user on every page view https://github.com/vercel/next.js/issues/51508.

Fuck 1MB of JS to render a static HTML page.

Fuck the image component, and not being able to optimise your image unless you use their cloud service for no reason at all.

Fuck spending 3 hours working out why you’re not able to use relative image paths in MDX files and have to shove everything in /public.

Fuck fighting five layers of configuration and bundlers and libraries and GitHub issues to try and load a WASM file without having the whole thing break.

Fuck some half-assed play at being a static site generator and a backend framework, that conveniently works best on your overpriced cloud service.

Use Astro. It’s what next.js pretends to be

https://astro.build/

Re: Next.js 14

#19

Post by hyperfuturism »

shmde wrote: post #5

Wait wtf, I clearly remember 13 came out of beta 4-5 months back. At this rate Next.js will be on version 20 by the end of next year.

It's been about a year since Next.js 13 - so a bit more than 4 - 5 months.

Re: Next.js 14

#20

Post by JCharante »

thinkingkong wrote: post #10

It's hard to take Vercel at face value these days with all of these improvements and announcements. Are we supposed to - in hindsight - understand that odd version numbers of their codebase were really just unstable releases all along? The app server implementation wasn't really meant to be used because it was an experimental release? I'm having a difficult time not being salty about this entire situation. There are…

I read the release notes but don’t understand what you’re talking about re: app router. They mentioned that they’re still supporting app router and pages router.
Post reply on HN