Next.js Conf 2024 Opening Keynote

[@franky47]

Thank you Vercel for sponsoring me and featuring `nuqs` in the keynote! 😍

[@JeffreyDahmer-n1y]

Our pleasure sir!

[@alexander.kachkaev]

Found my avatar at 2:18, wow 😳 Kudos to the whole community for making Next.js better and better! I remember days when there were even no API routes 😅

[@franky47]

I remember the Zeit days when Guillermo had a beard & long hair 😅

[@matiasask3774]

There's out a lot of haters that really don't understand the quality and the really complex task to create and build an util tool like as a Next js. I really love Next.js and I think it's a great tool.

[@jackdanielson1997]

Until you discover Remix and realize how needlessly slow and bloated Next is

[@rand0mtv660]

@@jackdanielson1997 Until you discover that Remix doesn't have all features Next.js has and is not a 1:1 replacement. Each tool has its own place and Remix is great as well.

[@loquek]

@@rand0mtv660 interesting, excluding RSC, what feature does nextjs have that remix doesn't? I know it has a lot more github issues!

[@MrEnsiferum77]

yeah, that's why u have vinxi and tanstack router, because it's very hard :D can't wait for post next.js era, never used, and never will. FIY, current project I work day to day basis, currently client only, is Tanstack Start ready, with next.js 14, it didn't starting at all.

[@jackdanielson1997]

@@rand0mtv660 Haven't discovered that yet, but let me know!

[@Vicsory]

Catching is doing great now 👍 😊 thanks

[@mm93249]

I love next.js + vercel and what they have meant for my little startup.

[@adityaanuragi6916]

What's the name of your start-up I wanna see the site

[@havefun5519]

Like: Make it work, then right, finally fast. Most of the time, I could make it work but maybe not perfectly right, and sometimes I usually spend lots of time want to make it all at the same time.

[@uthman.h]

lovely content, cant wait to start building..

[@DimitarDanailov]

Is it possible to add quick link for each sub item in the presentation ?

[@PradeepKher]

@vercel can you shar that demo project?

[@chrisalupului]

Thanks Vercel Team, with these updates how do you all go about handling the security and protection of sensitive environment variables.

[@nabinpoudel]

Love Vercel and Next.js ❤🎉

[@MightBeRasor]

me: "I use next because of dx" the "dx" walking into the stage:

[@flashbyte]

I located Sukuna, Toji and Po in the contributors list

[@ZaffarAli-g5i]

I need vercel link methad please

[@JamesPickering-s2l]

Or as we say in the trade "Get it working first, then optimise after". By the way when we can get production grade form validation out of the box without a new form validator library every year? Formik, Reactive Forms, JSON dynamic forms, Easy Forms etc etc.

[@rand0mtv660]

I've been using react-hook-forms for last ~5 years or so. Not sure why would you have to switch form libraries every year.

[@JamesPickering-s2l]

@rand0mtv660 Compatibility issues and redundancy.

[@charliegmeyer]

i

[@mm93249]

That’s so cool that Toprak joined a street gang.

[@AlwaysWeb]

For more awesome nextjs!

[@asadanik5987]

make it more backend heavy from frontend only. I think this will make it compete directly with fullstack frameworks more. I love if its happens

[@mertdr]

Am I missing something here or they killed SSR completely? According to the presentation of use cache and suspense, you must wrap a server component in suspense and get data on client if you want uncached fresh data on every request. Sort of like simplified react query. I don’t want to make comments on pure conjucture since not enough information given yet. But the examples show that if you don’t cache page or queries, you can forget SEO. And worse, you cannot make queries in Page.tsx if it’s a server component, which means you have to make fetch/db query in another component inside suspense then you must use another component inside of it for use client (in most cases you need it). Honestly I wouldn’t mind experimenting interesting concepts, that’s why I like nextjs but if “unstable_cache” is legacy now and deprecated, I’d really like to see a thorough concept for replacement. I hope they don’t ditch important concepts like server components (direct uncached query in page.tsx) in favor of faster page loads. Speed is vital but accessing fresh data without loading spinners or skeleton is much more important.

[@nikako1889]

any suggestions how to build next-flights app?

[@VercelHQ]

github.com/vercel-labs/next-flights

[@nepalrameshwor1540]

next js 🔥🔥🔥

[@Kane0123]

OpenNext letsssgoooo

[@Altroo]

bro what is superman doing here ?

[@JamesPickering-s2l]

Where are the "I want to break free" and "Radio Gaga" memes? 🎸

[@damar1967]

turbopack vs the world

[@theenriquecarbo]

Nice

[@signalsensei]

yehhhhhhh!

[@KnowledgeDBman]

OpenAI has moved from NextJS to Remix. Why?

[@jackdanielson1997]

Performance and memory. I work for a large corporation and we are moving to Remix because it’s much more lightweight and gives us all things that we want from Next and it’s faster, uses less memory, and also more configurable via Vite. It’s such an obvious choice, it has required zero convincing.

[@Abhishek-my2pt]

What about remix moving to react router 7 and no longer maintaining remix library?

[@seethruhead7119]

this is truly no longer javascript

[@tomspatula616]

👋

[@sks894]

Second!

[@arielton]

4th!

[@th3pr01234]

L crowd, no one laughing at Guillermo's jokes :(

[@KennBenin]

Sixth!

[@giggitygigs]

Third?

[@pequod4557]

Your thumbnails aren't KZbin friendly @vercel

[@mathesonstep]

First?

[@shafu_xyz]

but can you make opennext.js irrelevant?