Next.js 12

#1

Post by jacobwg » Tue, Oct 26, 2021, 3:37 PM UTC

Re: Next.js 12

#2

Post by leerob » Tue, Oct 26, 2021, 4:25 PM UTC

Hey everyone, Lee from Vercel here! Happy to answer any questions about Next.js 12. Personally, I'm extremely excited for the new Rust compiler.

Re: Next.js 12

#3

Post by capableweb » Tue, Oct 26, 2021, 4:29 PM UTC

Nice, a completely new attack-vector: https://nextjs.org/blog/next-12#url-imports Documentation still not there, so can't check if they actually compare any checksums or anything.

They also introduce their own `next.lock` which supposedly new tooling have to built around as well. Versioning management? What, we don't need that for where we're going.

Finally it's fun to see it ending with:

> We set out to build a zero-configuration React framework that simplifies your developer experience.

And if you read the beginning, you'd see:

> Middleware enables you to use code over configuration

I guess replacing configuration with code is one way of achieving "zero-configuration".

Feels like all tooling starts out with "We're simple, no config or code needed!" and eventually ends up so extensible that it's hard to figure out how to even use it. Then another competitor appears and shouts "We're so simple compared to X, no config or code needed!", and the cycle repeats.

Re: Next.js 12

#4

Post by [deleted] » Tue, Oct 26, 2021, 4:30 PM UTC

[deleted]

Re: Next.js 12

#5

Post by emadabdulrahim » Tue, Oct 26, 2021, 4:31 PM UTC

leerob wrote: post #2

Hey everyone, Lee from Vercel here! Happy to answer any questions about Next.js 12. Personally, I'm extremely excited for the new Rust compiler.

What's the timeline on React Server components? It seems next 12 experimental feature of Server component is a very early look? Since React 18 is not out yet, and it's not planned to have Server component in that release.

Re: Next.js 12

#6

Post by meowtimemania » Tue, Oct 26, 2021, 4:32 PM UTC

leerob wrote: post #2

Hey everyone, Lee from Vercel here! Happy to answer any questions about Next.js 12. Personally, I'm extremely excited for the new Rust compiler.

Can we still use obscure babel macros with the new Rust compiler? And if so, what do you think the future will look like for babel macros in a future where most build tooling is written in languages like rust/go?

Re: Next.js 12

#7

Post by ilovecaching » Tue, Oct 26, 2021, 4:32 PM UTC

Seems like a ton of tools/dependancies/frameworks to do something relatively simple. What is the benefit of this over using Hugo with Go templates?

Re: Next.js 12

#8

Post by leohonexus » Tue, Oct 26, 2021, 4:32 PM UTC

leerob wrote: post #2

Hey everyone, Lee from Vercel here! Happy to answer any questions about Next.js 12. Personally, I'm extremely excited for the new Rust compiler.

Is Next.js Live only available if the project is hosted on Vercel?

Re: Next.js 12

#9

Post by dude187 » Tue, Oct 26, 2021, 4:33 PM UTC

capableweb wrote: post #3

Nice, a completely new attack-vector: https://nextjs.org/blog/next-12#url-imports Documentation still not there, so can't check if they actually compare any checksums or anything. They also introduce their own `next.lock` which supposedly new tooling have to built around as well. Versioning management? What, we don't need that for where we're going. Finally it's fun to see it ending with: > We set out to build a zero…

Anything sold as erasing away reality eventually becomes overly complicated, as you inevitably have to work around it to address reality

Re: Next.js 12

#10

Post by dmix » Tue, Oct 26, 2021, 4:34 PM UTC

The big innovation here seems to be https://swc.rs/

If it works as advertised this is going to be great for a ton of JS/TS projects. Particularly having a 20x typescript compiler boost when running large test suites would be great. Maintaining 5-8 different babel related projects in packages.json is also annoying and often buggy.

Looking forward to see where else this gets adopted and it's stability.