Next.js 13… this changes everything

[@geeshta]

In NextJS 14, each component will be directory based and each html tag will get its own file.

[@uselessandempty]

U will never have to write `import` again... rails PTSD kicking in

[@Patrickdaawsome]

​​@@uselessandempty rails is great though

[@Rogueixpresents]

bro u dont even code

[@youarethecssformyhtml]

Didn't age well

[@Mauro-bs2lo]

wtf, i haven't worked with Svelte but the little I know about it sounds like what you just described?

[@michael.knight]

It was a 1:1 copy of an Apple keynote. They even used the silly ' the XYZ you know and love' that Apple always overuses.

[@J1Jordy]

Remix users being the Android users in that context.

[@hrclful]

... One more thing! You've to rewrite everything.

[@vapeurdepisse]

Yeah all these startups and even a bunch of large companies (ex Nvidia) have been copying the Apple keynote format for years. But Vercel ain't Apple, so why not be a little more humble for once?

[@zoladkow]

yeah, don't you just love how companies tell you that you love their products? makes life so much easier, just sit back and consume what'e given 🤷

[@lowwastehighmelanin]

Yeah it's annoying

[@nonstopper]

I literally was just researching nested layouts in NextJS like crazy and was amazed at how they weren’t implemented. Thankfully we finally have a real solution

[@santhosh3374]

You can just use remix js

[@ceopaludetto]

Remix has a way better solution, react router > next router

[@nonstopper]

@@santhosh3374 Have yet to try remix. Will have to give it a try

[@hugodsa89]

You can do nested layouts already without Next13

[@hugodsa89]

@@nonstopper what’s in your opinion worse? I’m my view seems like the getLayout is actually a better solution because it’s injectable at the component page level so your nested layouts are not tied to the route and it’s children.

[@2115-l9o]

By the time TurboPack is ready for production, Vite team will drop their version 4.20 with cutting edge technology providing a blazingly fast build speed which is (said by themselves) 69x times faster than TurboPack. I'm calling that!

[@Fernando-ry5qt]

The packaging tool war begins....

[@EugeneBuvard]

vite uses golang. Turbopack is probably faster only because it is using rust but at the expense of more complexity in the code. It will be good if they manage to finish it properly

[@kasvith]

@@EugeneBuvard Vite can switch to turbopack from esbuild though, they uses it because its fast enough for many cases

[@hanes2]

Evan you said they could add SWC to vite but it results in 58MB more bloat…. Which they don’t want, but react devs, they want the bloat

[@failist9570]

Evan You (creator of Vite, Vue) is just awesome man.

[@delavalom]

Amazing how the conf was yesterday and you already have the knowledge well known to be able to guide us through the Next 13

[@badalsingh1150]

animated Box With CSS kzbin.info/www/bejne/nXPQqWaIormbeqc

[@bvzpRTZMJQmKiWAFyohH]

I like how nuanced you present the changes and give props to the people in the community.

[@badalsingh1150]

animated Box With CSS kzbin.info/www/bejne/nXPQqWaIormbeqc

[@4.0.4]

Personally I think the constant release of "groundbreaking solutions" is more of a testament to the sea of self-inflicted problems in web development.

[@TheGreySage0]

Agreed,see u at the stake 😉

[@ja31ya]

Underrated comment; truth.

[@Lordzeus86]

I agree 1000%

[@mattc16]

Why would you say that? Literally every new solution has taken pieces of the previous solution or the previous solution had a specific use case where it is more advantageous to use than the new solution. We're literally back full circle with server side rendering and trying to keep as much JS out of the client as possible yet we're using pieces of every previous solution to make something FAR superior in terms of DX, UX, security, and performance. In fact, I don't remember the majority of the JS userbase "reverting" back to a previous solution without taking something new with them ever. The JS ecosystem just moves vastly more fast because it is built DIRECTLY on top of open source, it's the only native programming language to the browser (the application that runs the internet and we will only be moving further and further into the web and out of the desktop and localized software), it has a massive amount of free or cheap educational content with a large number of educators being highly successful, etc. etc. There's no other language out there that will ever be able to compete with the sheer quantity of JS developers out there. Most other languages revolve around proprietary code that will never be shared and built on top of along with only having a small fraction of the # of devs that JS has.

[@baldcoder_]

Yeah fuck these groundbreaking solutions. Quick question: How many decent-sized web apps have you built with vanilla JS? And how long did it take you?

[@DK-ox7ze]

Yeah okay. Javascript devs will never go out of jobs even when AI is ruling everything else, because the unemployed humans will be spitting out new JS frameworks and major changes every day. So yeah keep doing this shit.

[@sneezingcat6221]

everytime i see a new JS framework released every few months i feel lile shooting myself

[@lawrencemanning]

@@sneezingcat6221 there are programming jobs outside of web/JS hell.

[@professor_ozzy]

@@lawrencemanning Like?

[@lawrencemanning]

@@professor_ozzy everything from embedded to (desktop) games. I’ve spent the last 25 years of my life programming for a living and don’t (yet) know a thing about JS. I plan to keep it that way for as long as possible. 😊

[@astroid-ws4py]

I much prefer to work on my "mathematical proofs for veryfing computer programs with Coq" than to enter the JS hell.

[@DominikGiroux7]

Perfectly timed as always, was looking at the new docs just this morning

[@mihajlomilojevic2793]

Where is new documentation?

[@badalsingh1150]

animated Box With CSS kzbin.info/www/bejne/nXPQqWaIormbeqc

[@haus_automation]

Mhhhh, I'll wait for the "next big thing" after Webpack, Vite and NextJS. Should be released tomorrow (?).

[@williammccullough5627]

My heart goes out to front-end web developers. Good luck!

[@rubenverster250]

thanks bro :')

[@badalsingh1150]

animated Box With CSS kzbin.info/www/bejne/nXPQqWaIormbeqc

[@dannydozie9683]

Hahaha... this is an epic comment. Yeah... thanks bro :')

[@WhatIsThis-zq4hk]

Why anyone would go into this mind-numbing field at this point is beyond me.

[@rubenverster250]

@@WhatIsThis-zq4hk Wait until you have to work with Salesforce. Literally Torture Chair

[@thesanjithkumar]

Just a week back completed my website using next 12.3. After seeing I was excited to migrate my project, but little did I know the differences in components, filestructure etc in 12.3 and 13. It was like a mini hell, almost all component started to break. At last I stuck to next 12.3

[@IAmOxidised7525]

Yo, next 13 is not production ready I think

[@thesanjithkumar]

@@IAmOxidised7525 oh thanks for the info I was carried away by the launch.

[@Chaaos2]

Glad I procrastinated on building my next personal site

[@TheEmolano]

If it works don't try to improve it

[@krishgarg2806]

I had made half of my site in next. Got bored of react so switched to astro + svelte lol.

[@imraninfrarote]

"All is fair in love and MIT Licence code" Made my day

[@JorgetePanete]

License*

[@dipanjanghosal1662]

@@JorgetePanete both are valid

[@StellaEFZ]

@@dipanjanghosal1662 No, it depends License is, in UK English, a verb. In US English, it's both noun and verb. Licence is, in UK English, a noun. It doesn't exist in US English

[@dipanjanghosal1662]

@@StellaEFZ that's what I said. Both are valid. The KZbin comments section isn't only for US.

[@StellaEFZ]

@@dipanjanghosal1662 No, they're two different languages, you don't speak japanese while writing portuguese

[@dawichii]

This is literally the response to sveltekit - Vite -> turbopack - same routing system without (+) - same way of data fetching just returning data Still missing some stuff like stores and modules, which I consider much better than useContext, but this is just amazing!

[@cezarmocanu5043]

I was just searching today for a video of yours about next 13, so I watched the one about next 12 a couple of times. You make awesome videos! Keep it up!

[@badalsingh1150]

animated Box With CSS kzbin.info/www/bejne/nXPQqWaIormbeqc

[@rulofmg]

There should be an AI that can automatically refactor a framework to the next version

[@arden6725]

It’s not AI because that would be unnecessary but vercel already provides codemod scripts for migration in some cases

[@sharafmakk2936]

With the amout of refactoring there's been, there might be a way to make an algorithm that does that

[@adamlul]

Not gonna lie, I was struggling to understand the concepts of Next13 after watching the conference, but this made everything make waaaaaaaaay more sense. I'm actually kind of excited for it now.

[@badalsingh1150]

animated Box With CSS kzbin.info/www/bejne/nXPQqWaIormbeqc

[@Duconi]

Many things in the video didn't make sense to me. But I don't know react or next. I usually work with Vue and nuxt. Maybe I just never had the problems next had with that frameworks. I don't know.

[@tehpson]

this is why I keep to backend where there is never any gamechanging updates

[@1wsm1]

Next vid python 3.11… this changes everything

[@sps014]

Also on how rust 1.64 and dotnet 7 changes everything

[@Karl_Jimmy]

Still slow 🥲

[@chfr]

I'd be more thrilled by this tbh

[@smitty683]

Except it doesn’t tho

[@rea9lizer]

Waiting for covering Node.js 18 LTS

[@iliatalebzade8751]

Well the thing is when someone chooses to become a developer it's just a matter of time before they learn how fastly-evolving this field is, so as long as the changes are there for good, I for one have no problems with them. great video as always, thanks for summing up a 1 hour video into 6 minutes :)

[@chris-pee]

Correction, a *front-end* developer.

[@badalsingh1150]

animated Box With CSS kzbin.info/www/bejne/nXPQqWaIormbeqc

[@KimSkogsmo]

I agree, as long as the changes are there for good once added, I welcome them mostly. Sadly it's quite hard in reality, I mean they released ISR in Next 12 something and already kinda deprecated it in the next (pun intended) major version.

[@migueljara9399]

​@@KimSkogsmo I do agree with you, I think that they should've been more consistent to their concepts implemented. But I have to say that this looks like an improvement in the long run. Having all of those concepts like SSR, ISR, ans SSG was quite... overwhelming for people trying to get into it. Nevertheless, they're going to be required for some time for any Next.js developer, but probably going to be totally deprecated in two or three years. As one comment said, I'm in favor of change as long as it is a "good" change.

[@mtgshmoopy]

I use SvelteKit in production because I'm a crazy bastard so a lot of these Next 13 changes are veeerrryyy familiar! They're even making the exact same switch to directory-based routing SvelteKit did a few months ago. Seems like developing in React is going to get a lot smoother! But I still prefer SvelteKit. No VDOM is very attractive since I often have to deal with third party web components. It's compiled so it's more opinionated but I like the opinions of the Svelte team. All these fancy tools are making JS dev a dream! The future is bright!

[@rawallon]

Not to metion that the best thing about using SvelteKit is being able to say you use SvelteKit

[@cookifymedia]

I totally agree. I think it's heavily inspired by SvelteKit and Rich Harris that convenient is working at Vercel. But nice to see next going this way.

[@ChrisJaydenBeats]

Now hopefully SvelteKit can start maturing. Especially much needed packages like Sveltekit Auth. Tons of OS projects that are trying to tackle it right now, but there’s no go to yet (for me at least).

[@wliaputs]

@@rawallon I use Sveltekit btw

[@fakenameforgoogle9168]

@@ChrisJaydenBeats lucia-sveltekit is a very promising package in early development

[@Joshfw27492]

Thanks Jeff, I commented in the general chat on Slack yesterday to see if anyone was attending the conference but no one responded. The main feature I was most excited about is the new data fetching capabilities. I always found myself in between a rock and a hard place determining between using getStaticProps or getServerSideProps or using the former with Incremental Static Regeneration. It appears that I will no longer have to worry about this with the latest version of Next.

[@ShafterPlay]

The structure of routes being folders, files for page, error, etc. looks reeeally similar to SvelteKit

[@VictorSamuelMosqueraArtamonov]

And really similar to PHP.

[@neociber24]

@@VictorSamuelMosqueraArtamonov going back to the root but type safe

[@TAINCER_]

I think you're talking about PHP 6 years ago.

[@sleekism]

They stated it took inspiration from SvelteKit, which is also kind of a Vercel product now with Rich Harris working on it and Svelte full-time

[@gyorgykovesdi]

@@TAINCER_ JSX itself is reminds me to PHP, but from 24 years ago when there was no templating systems and you had to write spaghetti-code :D Someone introduce them the "Smarty", maybe they can learn from that something.

[@nro337]

Thanks for including the parcel mention here, saw Devon's tweet and think it's important to credit where their inspiration probably came from

[@BrianBest]

I feel like I woke up in 2010 and stumbled in to a Rails hype fest conference

[@user-qy2wf2lt6v]

This ...

[@codinginflow]

I'm currently refactoring a project from /pages to /app and I don't find the changes that dramatic so far

[@2bfrank657]

This is why I never got into IT professionally - the constant need to learn the "next best thing" rather than having the ability to actually master your tools.

[@ihate4chan]

Only frontend web dev changes so rapidly

[@Nemcoification]

It's bad when it comes to front-end, but even in front-end tons of companies will default to the standards rather than chase the shiny new thing. Outside of that it's much more stable. You might want to reconsider ;)

[@AttackHelicopter64]

you don't most projects use something more stable and battle-tested, that will allow to do any request from the customer cause you can't really say: "Hey, this app doesn't work as you wanted, but we are waiting on shitty_useless_after_two_days_framework v.14.5+ to solve this" or "we can't find any developer that knows blazingly_fast_and_two_years_learning_curve++, so we can't hire anyone for 6 months" or "we just need 2,5M $ and two years to rewrite our current project, so we can test out these new and very important (for 1% of people) features"

[@2bfrank657]

Thanks for the replies all. Yes, I guess it's easy to watch all these videos and develop the misconception that every project is built in the latest whiz-bang framework. Pleased to hear that devs are focusing on reliability over novelty.

[@IvanRandomDude]

@@ihate4chan Actually, other parts changed even faster. Going from monoliths and MYSQL deployed in my mother's basement to microservices with distributed databases, sagas, event sourcing, event streaming and billion other patterns, hosted on EKS in span of 6 years is not a change at all, I must be dreaming.

[@vmia159]

5:17 sounds fun. I guess I am going to learn it after a year which until majority of people move on and I will never gonna migrate it with current project.

[@zPiranhaz]

1:37 that's what I immediately thought hearing the previous statement. 10x faster than Vite doesn't sound like that big of a deal when it's already fast enough. I'd rather not make that trade when it adds more extra work.

[@yt-sh]

6 minutes. 👏👏👏 6 minutes is all it took to clear these concepts, you're a great teacher! thank you!!

[@StephenGillie]

Software development isn't about making websites in a simple way, but about making Rube Goldberg machines that display websites as a side effect.

[@WhatIsThis-zq4hk]

Literally why I left the field. It’s a nightmare.

[@tomaszsikora6723]

They finally did it, nested routing with layouts. Now I can finally start a project in next.js

[@Fernando-ry5qt]

Wait that was stoping you? Why? You could have just nested layout components haha

[@berrywarmer11]

@@Fernando-ry5qt would they have been BLAZINGLY FLAST ™ though?

[@Fernando-ry5qt]

@@berrywarmer11 you win

[@jmg9509]

Can always count on Fireship to remind me of how little I know as a 1.5 year old self-taught developer :")

[@meganaut5294]

Same, except as a 26 years experience dev. You’ll never know it all.

[@ypeelsleepy]

@@meganaut5294 ^yeah kinda feels as if you learn something and by the time you feel comfortable using it ist obsolete ^^ I love being a developer.....

[@eagl3007]

lol I was about to say... i'm out here with 10 years of messing around in web technologies and i feel like every month I see some younglin' come up with a hot new catchy name framework. such is life

[@coconutflour9868]

pretty impressive to be a developer at only 1.5 years old

[@williamrgrant]

@@coconutflour9868 kids these days...

[@md.fazlulkarim8847]

Old Projects: I'm going to pretend there isn't an update! New Project: Come baby, light my fire!

[@terraflops]

i want to learn JS framework but each week you make a video that makes me wait to see what else will be available

[@JorgetePanete]

New Rust Frameworks™

[@suri5023]

i belive with that mindset you'll be waiting for a long time and you won't learn anything in the meantime. just start learning something it doesn't matter that it won't be the most new thing in a couple months. don't waste your time like i did best of luck to you

[@glardian966]

Why would you WANT to join this roller coaster?

[@terraflops]

@@suri5023 Svelte framework interests me, looks more friendly. // I agree, just dive in into something and see what happens

[@mattlewis8457]

Just learn Javascript, don't focus on a framework. They'll all make sense if you're comfortable in JS.

[@heygema]

Fireship is the most entertaining yet educative creator out there, lmao, like the videos are actually that addicting.

[@user-ur3sj5eh1h]

Whenever I hear Blazingly Fast , ThePrimeagen immediately pops into my heads

[@21Blankenship]

“Now I know you just switched over to the next gen build tool Vite last week” hit way too close to home

[@gtmoyo]

It took me 18 minutes to watch your video because my slow brain had to stop, replay, and digest everything you said. But I wouldn’t have it any other way. Thanks for the overview!

[@xaxfixho]

kwanai blaz 😒

[@BaldeepSingh24]

Thank you for doing this! And thank god for your channel, always top notch quality!

[@nero1375]

Wait, Vue and Nuxt don't already do this stuff about years from now?

[@Trzimajewski]

bro, that was the best next release until now, amazing, been waiting so long

[@tomrowe2181]

I feel like this is a change that you'd never adopt over Remix or similar frameworks. Next's strength is its huge community and solidity in the industry, you know it's not the best but someone would have done what you want to do before and you'd likely be able to find their code. Pick a much leaner framework if you want this DX

[@ashishverma9840]

feels good to watch your videos.. after banging my head with Typescript :)

[@ba8e]

Awesome! A couple more versions, and this may barely touch Svelte.

[@Alex-xl4xe]

I literally just finally got into Next and managed to understand the basics and they just went overboard with that, lol.

[@ricardofabilareyes]

It continues to amaze me how JavaScript guys just keep reinventing basically PHP 😂

[@datoubi]

I know Javascript, Python, C++, some Rust, some Go, some Java and some PHP and I'd say that PHP is by far the worst language. No static types whatsoever.

[@rishabsharma5307]

Was eagerly waiting for this 🔥

[@lcarv20]

Specially the new routing design reminds me of sveltekit, which is not weird since sveltekit is being supported by vercel. I like what they are doing :)

[@a-fletcher]

I was about to say that it sounded like they added remix like features, then you bet me 2 it in your own vid haha. Sounds like some nice changes. I'll still stay with remix for now though.

[@iLiran]

as someone who is learning react , I would really appreciate a focused front/fullstack roadmap with the most needed technologies.

[@vapeurdepisse]

@@justinsalcedo2678 looks like a keyword dump on a 40-page Indian developer resume.

[@Mogwai88]

@@vapeurdepisse lmao so true

[@justinsalcedo2678]

@@vapeurdepisse Not gonna lie, it may look like a keywords pool. But it's useful when you don't know where to start from as a beginner

[@TheAliceQuo]

@@justinsalcedo2678 jesus christ my ADHD can't even look at that website for more than 3 seconds.

[@WhatIsThis-zq4hk]

“Focused roadmap” and JavaScript don’t go together

[@alvina.6854]

that meme at 5:27 way too relatable OPTIONS API FOR LIFE

[@stevemcwin]

Hey Jeff, could you do a video explaining the Nim programming language in 100 seconds please?

[@badalsingh1150]

animated Box With CSS kzbin.info/www/bejne/nXPQqWaIormbeqc

[@stevemcwin]

@@weakspirit_ the only time he mentioned it was in the programming iceberg video, but I think it's cool enough to be covered in a video of it's own

[@theghostyced]

Yep the same thing i thought the moment I saw the new features. Most of them were already implemented in Remix, Next is trying to catch up

[@adamwright261]

Yea...this is why I love Angular being a one-stop-shop for basically everything.

[@Jurisabc]

I just love the low-key dissing vibe of Fireship's videos!

[@marswor]

awesome, now we gonna get even more 'index' like files throughout the codebase xD

[@moder2011]

I came from the future and I am telling you it's nightmare i have index.ts(x) for everything 😭

[@heddshot87]

420 seconds 😆 you're taking absolutely every opportunity to joke around. Love it!

[@bungbloopity]

I was just thinking this morning that it had been a little too long since the last game-changing JS framework. Its been almost a week 😅

[@NNNedlog]

Thanks for always keeping us up to date

[@Thikondrius]

It's been 0 days since a new js framework has been created.

[@codewithguillaume]

I was there yesterday… I saw what they are capable of

[@mikeeomega]

Web Developers: It's the end of Vite Evan you: If this proves to be the shit, we replace rollup for turbopack Parcel: I've been the GOD for a long time kidos

[@winstijnsmit3752]

Very cool that you included the Goliath at 0:30. I went to that theme park this summer!

[@maxxkax]

News of the year: Now you can make routes by putting files in folders! Just like the web used to work for 20 yreas! :D Web3 == Web1

[@arden6725]

Web3 is just a buzzword, and this isn’t even Web3

[@hybs9473]

Double equal? Really? Jk

[@MehmetKoseDev]

Right on time Jeff. Thanks. Hi Jeff's mom

[@sandeepsai5224]

Isn't sveltekit already has the layout and +page.svelte thing. Also sveltekit has the similar data fetching by exporting load function in the +page.svelte page

[@tentacle_sama3822]

Can't wait for the full 13 tutorial

[@jackcriss100]

well done! I'll keep using remix.

[@sumtingwongwe2low]

would love to get some peoples opinions on this, Im a react front end developer with a bit of experience with firebase, node js/mongodb/express/mongoose and i have worked a bit with nextjs 12, it seems to me that with these new features, i should make projects with nextjs 13 instead of really anything else?

[@juniorgarcia3595]

Incrementaly adopted, 1s after **deletes the pages folder** 😂, I love this kind of things in your videos

[@ryangrogan6839]

Node is starting to look like something worth my time. I prefer frameworks like Django and Flutter. Seeing things move toward improving the developer experience is nice. I can't tell you how many times I run into something in a framework that requires way more effort than it should take.

[@AkshayKumar-kz6zh]

I started out my dev journey with Django and soon realised there are very less jobs compared MERN. Spent 6 months learning MERN stack

[@georgios_georgiou]

Now this brings the outro … will see you on the NEXT one to a whole new level ! Good summary of the keynote definitely killed this one 💀

[@ebirimuchechukwuprecious3658]

I have been using Angular for over 4 years. I keep seeing new JS frameworks and stack an average of 6 months. I never learn any. I am still learning angular. "I fear not the man who has practiced 10,000 kicks once, but I fear the man who has practiced one kick 10,000 times." Bruce Lee

[@wahoobeans]

Good luck on your next job search / job.

[@jordanribbink1991]

If the only tool you have is a hammer, it is tempting to treat everything as if it were a nail Maslow

[@maxcharacterlimitreache-]

I love your channel more and more As im continuing my beginners part of learning to code and building some test projects it is also starteing to make some sense. I'm thinking about saving up for the lifetime pro subscription on fireship

[@cgeidt92]

Nuxt 3 vs Next 13 would be awesome!

[@sanusihassan7125]

I'm very happy when I get notified that there is a new video from fireship

[@WhatIsThis-zq4hk]

All these JS frameworks claim to solve problems, but they don't solve the biggest problem of all: too many JS frameworks

[@ba8e]

Hold on, I'm working on a JS framework for that!

[@WhatIsThis-zq4hk]

@@ba8e whatever. Just don’t call it “bLaZiNg FaSt”

[@pauhull]

0:30 that's Goliath at Walibi Holland before the repaint

[@Ali-Aljufairi]

We need Next.js 14 update

[@ThunderboltPath]

5:43 the amount of JS being shipped to client-side remains the biggest drawback of Next.js

[@hi9313]

I used to use just preact with static build for this reason, however, next.js is where the jobs continue to be, so meh. Thought the next major release would finally solve this problem. It is surely just a simple rehydration problem off the back of a bootstrap js snippet. so frustrating...

[@punchcake4832]

soon we will be shipping the whole web in next.js but dont worry there will be the 234038 runtime to speed things up by 900x (all of this just to center a div)

[@ThunderboltPath]

@@punchcake4832 I see what you did there, haha

[@ThunderboltPath]

@@hi9313 except if one day the job might not be there anymore... What's next? (pun intended)

[@riddixdan5572]

that's why I like remix, you can pretty much write react on server side but you can also ship 0 js to client if you really want to.

[@naveedalirehmani4135]

Next 13 is amazing in every way. As amazing as next 12 was, next 13 takes this to a whole new level. My favorite thing about next 13 is that it uses page caching to get behavior like SSG,ISG, and SSR, which can be hard concepts for newbies to grasp

[@howl2339]

So thats what came next. I just wish the framework was more reactive

[@bahibrahim101]

Thanks for the video and see you in the next one.

[@XoStefan]

the "new" routing seems an awful lot like SvelteKits new routing that was released a couple weeks ago 🤔

[@Mkrabs]

"this looks cool.... yoink!"

[@JimmySting]

Yeah...and that update does support API routes with its directory paradigm. The "+" file prefix had a bit of an initial shock, but I've warmed up to it.

[@philheathslegalteam]

RFC was released months ago for next. Rich harris Even said he copied it for Svelte

[@silasobviously]

SvelteKit is such a joy to develop with. Never going back!

[@user-ws2et9el2z]

Great! Want ScalaJS next :)

[@catholic_zoomer_bro]

So every Next version is a game changer?

[@mikep1468]

Excellent video! Is the expected link to your new Beyond Fireship channel missing from the text blurb below the video, or did I miss it? Either way, I found it & subscribed, and am looking forwards to your Next.js 13 tutorials over there!

[@dc22199x]

The page and layout is more likely inspired by sveltekit than remix 😂, later phases they will be copying the load() and actions

[@jatinhemnani1029]

Rich Harris creator of Svelte now works at Vercel and contributing to Svelte full-time so they must have decided this

[@roberthall9452]

SvelteKit drew inspiration from unreleased NextJS.

[@uwuxdmusic]

This is my morning news with a cup of coffee ☕

[@Matrium0]

Damn, the rise of new build-tools every year makes me glad I use Angular. Build is certainly on the slow side (2.5 mins for a medium sized project), but good enough for the customer and me, so I never even tried to optimize it. Great video and it does look really nice! Their presentation turns me a bit away though, "blabla our framework heals cancer blablabla" :D Also: how fast do you need it? Made a demo project with Vite some time ago and it is fast as hell. It's nice when something is "10 times faster", but the drop from 10 seconds to one second is just not the same as from 1000 to 100.

[@leezhieng]

My static HTML page is hella fast too lol

[@Macchiatobaer]

A Video about Cloudflare Workers and D1 Database from you would be the butter to my bread.

[@macchiato_1881]

If developers put the same effort into solving actual problems the same amount they make new JS frameworks, we would literally be a type 1 civilization by now.

[@paradiseexpress3639]

Problems like what david?

[@macchiato_1881]

@@paradiseexpress3639 problems like you

[@paradiseexpress3639]

@@macchiato_1881 David, stop being a doofus and explain yourself

[@imsarvesh_]

4:37 Everything is fair in LOVE and MIT licence. You just killed it man.

[@SXsoft99]

I see so many similarities with old php frameworks

[@khangle6872]

Full circle i guess

[@Clientastisch]

I just started today with nextjs and everything I thought was shitty has been resolved.

[@riddixdan5572]

when I was watching the conference yesterday, all I heard was just buzz words and alpha/beta features that are already stable in remix js. kinda disapointed and scared that nextjs might get balsy and just "buy" react from meta. also, as others have mentioned, the presentation was almost one to one from apple in the sense of style. also, about shiping 0 js, remix can do that, so there's that.

[@maharta8458]

Don't think meta will sell react though

[@thekrixhna]

Great video! How about a video on Backend development in 100 sec

[@fazzitron]

The constantly changing landscape of Javascript makes me glad I use Django

[@Enigmata23]

Yup. Its the exact reason I switched to Python and now building fullstack projects with Django. The JavaScript eco system is literally hell, you cant blink without a new framework/code breaking update coming out

[@ulisesavila2879]

You are good. Really. The majority of "spa" apps doesn't even need react and all that

[@sidkapoor9085]

django is backend tho

[@muslim8622]

You have the point, haha. But the main difference which is the main problem also, beetwen Django and the JS framework like Next JS, Gatsby, Qwik and so on. It's the purpose. Django, it's straight-forward because we have just the server side to deal with. The JS frameworks have the "good" idea to mix the server side and the client side concerns for the client it's a awsome experience (i guess, maybe...) but for the developers that's a real mess to deal with ^^' Howover, there's also framework JS which not handle the client. render one time and it's over (maybe some API). But now the problem is, who want to code in Javascript (by choice) ^^

[@turolretar]

If we’re gonna go there then simple html is good enough for most things

[@eliav3]

I do you make all these amazing videos that rapidly? you are really one man army!