Live data from Hacker News

Next.js 13

nextjs.org

11–20 of 106 posts

Re: Next.js 13

#11

Edit: There's some more discussion about Turbopack at https://news.ycombinator.com/item?id=33333695 . Looks like they launched a webpack alternative called Turbopack today: > Next.js 13 includes Turbopack, the new Rust-based successor to Webpack. https://vercel.com/blog/turbopack https://turbo.build/pack

Spent the last few months migrating to Vite. The Javascript ecosystem is exhausting and exhilarating all at the same time

Re: Next.js 13

#13

// "alt" is now required for improved accessibility I'm all for accessibility, but let us decide when to implement it.

You should still be able to use alt="" to indicate that it is "decorative" and not meaningful imagery for a visually-impaired user.

Re: Next.js 13

#14
post #9

Edit: There's some more discussion about Turbopack at https://news.ycombinator.com/item?id=33333695 . Looks like they launched a webpack alternative called Turbopack today: > Next.js 13 includes Turbopack, the new Rust-based successor to Webpack. https://vercel.com/blog/turbopack https://turbo.build/pack

Sigh another one? I thought Vite was the new thing.

Sigh? I think the speed improvement is awesome.

Re: Next.js 13

#15
Their tutorial is incredible, everyone should take a lesson from Vercel on this: https://nextjs.org/learn/foundations/from-react-to-nextjs/ge...

Tell me:

1. What I need to know to understand this documentation

2. The before state (plain React.js)

3. The after state (Next.js)

I'm fucking sold, I'm going to use Next.js just based on how well written this documentation is.

Re: Next.js 13

#16
Surprisingly, my compile times with Next.js 12.3 have been really really awful. A simple CSS change takes almost 10 seconds to compile and I'd love to know why.

My app isn't complex, it uses Recoil, Tailwind and that's it. Compile times were better in v11 in my experience.

Re: Next.js 13

#17

// "alt" is now required for improved accessibility I'm all for accessibility, but let us decide when to implement it.

> I'm all for accessibility, but let us decide when to implement it.

Which usually means never.

Re: Next.js 13

#18

Their tutorial is incredible, everyone should take a lesson from Vercel on this: https://nextjs.org/learn/foundations/from-react-to-nextjs/ge... Tell me: 1. What I need to know to understand this documentation 2. The before state (plain React.js) 3. The after state (Next.js) I'm fucking sold, I'm going to use Next.js just based on how well written this documentation is.

I'm totally biased here but I've been super impressed with the documentation culture at Vercel. Definitely a high high priority internally.

Re: Next.js 13

#19

Edit: There's some more discussion about Turbopack at https://news.ycombinator.com/item?id=33333695 . Looks like they launched a webpack alternative called Turbopack today: > Next.js 13 includes Turbopack, the new Rust-based successor to Webpack. https://vercel.com/blog/turbopack https://turbo.build/pack

Spent the last few months migrating to Vite. The Javascript ecosystem is exhausting and exhilarating all at the same time

No telling how many sides the next iteration of the wheel may have but one thing's for certain: That one will be the ultimate version.

Re: Next.js 13

#20
The next-gen bundler rewrites are getting insane, just as things were consolidating in the other parts of JS. We now have:

- EsBuild

- SWC (also written by someone who works at Vercel)

- TurboPack

- Vite (rollup)

- Parcel

- Rome

I've noticed in the javascript ecosystem there is much less convergence than in other languages. Everyone wants a flag in the ground.

Post reply on HN