The Story of Next.js

[@hassaniyouness8024]

what I love about this series is how it combines the history and evolution of a problem so you can see very clearly why we ended up here, great work Tyler!

[@uidotdev]

Thank you so much!

[@theMadZakuPilot]

I fully agree.

[@masternobody1896]

@@uidotdev nice

[@AmanGupta_Dev]

True that !

[@HermanWillems]

And here we are writing front end with Rust compiled to webassembly

[@daveisdead]

I’ve been a nextjs developer for the last year and I am blown away how developer friendly it is. Every feature is better than the last

[@uidotdev]

Agree. Thanks for watching!

[@daveisdead]

@@uidotdev your channel is going to blow up! Your production value is through the roof and content is amazing. Gonna hit 500k before you know it

[@ayandak47]

Ca I check out what you have built? I am just about to build an events site with Strapi back end for Auth and cloudinary integration.

[@myschiefmuintir7357]

I just picked it up yesterday as someone who's used react almost exclusively and I absolutely love it. It's so intuitive

[@atoledo]

Tyler, you're like a companion for all of us technologist overwhelmed and fatigued by the vast amount of technological desicions we have to make every day. Thank you!

[@uidotdev]

Thank you so much for the kind words. ❤️

[@Utopy34]

Awesome video! I've been a professional AngularJS then Angular developer for the past 10 years and I'm shifting towards NextJS because I really think this is the future of web apps. The simplicity of nextJS is just stunning, you don't have to create lambda functions and build an entire API gateway in AWS to get things going. Combining it with Prisma and PlanetScale is just absolutely amazing. We are also finally moving away from Redux and towards smart key-based stale-while-revalidate caching mechanisms that make the UI even faster and simplify the development further. Soo soo good! Best time to be a web dev!

[@uidotdev]

Agree!

[@ulisesavila2879]

In another perspective I am tired of the fragile nature of react ecosystem and I am trying to divorce from it jumping to angular. Granted I have not tried next

[@Utopy34]

​@@ulisesavila2879 It actually depends on which projects you want to work on. For enterprise clients you need angular and will mostly build large/complex B2B or SaaS products following strict angular conventions and SOLID design patterns. That's what I've been doing and it pays really well. For startups or complex B2C projects React or NextJS are better but the code will be harder to maintain and the quality will likely degrade over time especially with new hires. These technologies don't compete with each other, they serve different needs on the market!

[@brentsteyn6671]

Svelte is better.

[@coolhunter3]

@@brentsteyn6671 Good luck finding a job with Svelte though.

[@imtanuki4106]

You have a real gift for explaining complex topics simply...and coherently...and conceptually. You would make a fortune if you created a series on JS and frameworks.

[@nathanrey]

Uploading this as a podcast would help me through my day

[@uidotdev]

Not a bad idea

[@codinginflow]

I love NextJS for how simple iot makes sever-side rendering with getStaticProps and getServerSideProps. It's so intuitive. SWR is also great.

[@busyrand]

You've managed to answer the "Why" behind the existence of this technology, which is something I've never heard explained well. Javascript frameworks have such annoying mania that I could never tell whether something was a real, viable technology or not. Very well done.

[@uidotdev]

Thank you!

[@romanvinogradovby]

It. Just. Brilliant. Masterpiece. Have no more words. Love the narrative style with all the video inserts from the past and present. You have covered the subject in great details. Thanks!

[@uidotdev]

So glad you enjoyed it!

[@aksh1618]

Wow this was amazing! As a backend developer whose exposure to the JS world has unfortunately mostly been through complaints of how bad it is, this makes me want to fire up a Next.js application right away and get started with exploring this whole new world!

[@uidotdev]

So glad you enjoyed it!

[@mrkinetic]

I like when people complain about JS. It's good for my job security. :D

[@Dipj01]

if you're a backend developer using any proper language+framework like Java (for Spring boot), Go, C#(asp), even php (for Laravel), Next.js will still probably be a downgrade for you.

[@ArrigoLupori]

This is incredibly good. I think it's the first time ever that I took notes on a KZbin video that wasn't supposed to be a study subject. You packed SO MUCH VALUE in 12 minutes, I can tell the insane amount of research behind it. Honestly, I'm impressed. I think I might have a new favorite channel :D

[@uidotdev]

That means so much. Thank you!

[@Zealwind]

Same here. Amazing content.

[@christopherappleby7453]

Dude exact same. Eloquent, concise, and extremely informative. Mandatory subscription.

[@dubola5777]

I wanted it to be longer because i enjoyed every minute of it. Thank you!

[@uidotdev]

❤️

[@robertodelgado1234]

Your signal to noise ratio is incredible. Great work.

[@uidotdev]

That's high praise! Thank you.

[@theMadZakuPilot]

I like how you always include the history.

[@uidotdev]

Thank you! ❤️

[@FinnReinhardt]

Lovely content. You just keep on delivering. I knew when I saw your first Video at just around a few thousand subscribers, your hard work would pay off!

[@uidotdev]

Thanks for the continued support Finn! ❤

[@yewo.m]

I really like your videos, especially your most recent ones, which are more like storytelling. I feel like the programming videos on KZbin are mostly full of tutorials, and there are less videos which look at things from a higher-level perspective as these ones do. Awesome work

[@dair4245]

this video is so great. as a webdev novice who came through the coding bootcamp pipeline, feeling a bit bewildered about everything going on in the landscape of webdev, this gives an essential look at the history of "what" i've been doing and why i am doing it. new devs are exposed to so many different technologies and stacks nowadays that i feel most of us have no idea why we use one thing as opposed to another. this video definitely provides clarity to novices about what the thought within the webdev community as a whole has been that has lead us to this point. thanks you for this content!

[@uidotdev]

That means so much. I'm so happy to hear it was helpful.

[@intenzi69]

If I may ask, could you tell a bit about what your coding bootcamp's curriculum was.. For example what languages it covered, how long the duration of it was, etc I am a beginner + self-taught programmer and would definitely like having some hands-on information about what I should be going for when learning js and other topics for tech stacks and how!

[@mirzaarabferuvian136]

I was frustrated for the past 3 months, as I have nothing to do in my spare time beside gaming. Just found out your channel yesterday and immediately subs with notification on. Thank you for giving me purpose to fill my spare time beside just mindlessly watching youtube short or and instagram

[@uidotdev]

So glad you find it helpful!

[@codewithguillaume]

This video is truly amazing. And true. Next.js though is not the only one today to carry such an offer and often some of other frameworks are doing better in my opinion such as Sveltekit or Nuxt. Thanks for this video !

[@SteveShaffer]

What a lovely and accurate and engaging and well-produced video. Well done!

[@minierparedes5177]

Your narration and the pace with which you provide us the information about the subject matter make these the best documentary series!

[@uidotdev]

That means a lot. Thank you!

[@aryamankukal1056]

this is srsly amazing; all this content is hella quality and I enjoy these videos a lot; keep it up!!

[@uidotdev]

Thank you!

[@mr-skorpion]

A very well put together video, enjoyed and learnt a few things. NextJS is definitely one of the best things to happen to front-end development in recent times. I love working with Next and emotion to make fast, reactive SPAs 🌸

[@uidotdev]

Thanks for watching!

[@sle6423]

Love all this historical context. So rare to see it discussed, and so well to boot!

[@uidotdev]

Thank you!

[@BaldeepSingh24]

Your work and this series is a masterpiece! The amount of reserach and work that would go into making such videos would be insane... And then you present it with so well, great work man!!

[@uidotdev]

Thanks so much!

[@dfuzerz]

Even though I started developping web stuff when I was 16 years old (I'm 21) it has always been hard for me to understand what every technology does, what problem it solves and how everything fits together. This video explains everything perfectly and I'm thankful I watched it. Thanks a lot !!

[@Taaz2]

I am a web backend engineer and it obviously comes with it's own culture like absolute disdain for anything frontal. Though, your videos, especially how you always explain the history of each project and it's building blocks, in a concise way is something I will gladly enjoy. Awesome work.

[@uidotdev]

That's the highest compliment I could receive. Thank you!

[@jpierce2l33t]

Ugh me too. All this Javascript garbage makes me sick, I can't believe people actually wanna use it server side now. But this video navigated thru the absolute mess that is the framework jungle quite well, while simultaneously reaffirming my feelings about front end work 🤦‍♂️🤣 - great video though, really!

[@uidotdev]

@@jpierce2l33t I'll take it!

[@jpierce2l33t]

@@uidotdev I mean honestly, I've never made it more than 5 minutes in of legit trying to grep front end stuff without going cross-eyed and promptly stopping...and you clearly explained a lot of it very well, in just a short video. Kudos to you!

[@samydjemai927]

Amazing content! i always struggle to explain the 'why ' of some technologies to my students. I'm now suggesting your videos.

[@uidotdev]

So glad it was helpful.

[@coderized]

Always great to learn more about the history of React!

[@uidotdev]

Glad you enjoyed it!

[@chrisl2773]

It's absolutely phenomal the rate at which the technology industry continues to grow. I remember when React started to gain traction, then the introduction to Next.js and now even frameworks that go even further beyond to solve the drawbacks of Next.js and so the introduction to frameworks like Remix have been made. Absolutely love it at the same time though :D

[@tony_wxyz]

Hey uitodev, just want to say this video was amazing. You are on the same level as fireship in terms of content and how you break it down. One day you will have over a million subs, you deserve it! Thanks.

[@uidotdev]

That means so much. Thank you!

[@ghaznavipc]

this video was better than fireship. fireship is good but tells things faster than my understanding...

[@akejron1]

@@ghaznavipc you do know you can change playback speed right? I like this fast pace, sometimes i do ahve to slow it down tho

[@ghaznavipc]

@@akejron1 I don't like to say bad things about fireship contents... but explanation of this video was way better and I understand it way better. it's not just about speed only

[@arthtyagi]

SPAs are pretty cool and have valid use-case when you're actually building an "app" (not a website), just make sure to use Vite (or something like Vite) cause that does tackle the issue brought up (large bundle sizes slowing down initial render).

[@dlongodesign7026]

I fell in love with NextJS, now I love it even more! Thank you for this video!

[@uidotdev]

Thanks for watching!

[@ChocolateMilkCultLeader]

Shared this with the readers of my coding based newsletter. Keep up the good work. Will be following your content very closely

[@uidotdev]

Thanks so much! Glad you enjoyed it.

[@kd7542ye]

Svelte is already what everyone is moving to and it is the best thing to happen to web development since JQuery IMO.

[@bradyfractal6653]

Yupppp Sveltekit is much better

[@uidotdev]

Svelte is great too.

[@Ivcota]

@@bradyfractal6653 Sveltkit isn't ready for production (for hiring companies) unfortunately. Ecosystem is weak but it'll be there soon. I'm jumping to the Svelte ship as soon as I see more jobs becoming available for it 😁

[@rumble1925]

@@Ivcotawhat ecosystem do you need? It’s javascript. Just use the quadrillion packages

[@khengari77]

​@@Ivcota Companies are slow to adapt but in itself Sveltekit is very ready for commercial scale usage

[@Agalin920]

Amazing video. Fantastic visuals and clean explanations. Please keep it up. I can see this channel becoming the next fireship.

[@uidotdev]

Thank you!

[@eric.m5790]

love this video and i love nextjs. I hope the react community takes on nextjs as the standard way of building react apps

[@uidotdev]

Thanks for watching!

[@stey]

This is such a well-narrated & produced video! Great job!!

[@uidotdev]

Thank you Steven!

[@truvc]

Isomorphic apps are amazing. This year is going to be an amazing year for the web. Page transitions, new color spaces, reactive programming and isomorphic apps will make web apps better than ever.

[@uidotdev]

Agree!

[@rodsimon7]

Binged all the "Story of..." videos. Awesome stuff. Will check out your other works. Subscribed.

[@uidotdev]

So glad you found them helpful!

[@EddyVinck]

Can’t wait for the Remix version of this

[@uidotdev]

Soon!

[@wishmeheaven]

I just saw this video, and I did what I never do: even before entering this video - I entered the channel. Then, read few video titles, and immediately, not as ever before, subscribed... Without even seeing a single video. Only then I've found myself here. But not before I see that there is no new content in this channel for a long while now. Why? You've something truly cool in your hands! A great concept, a great content, a great approach, a great editing, a great perspective... Maintaining an active dynamic channel is a challenge, but as a person who appreciates quality - I must say: Do appreciate your creation and keep uploading a new content. I wish you the best of luck. You're awesome. Just make sure to show it much more often..

[@uidotdev]

We'll be back soon!

[@cricketbeyondlimits]

Hi Tyler, You got a sub. Really amazing breaking it down into pieces so that we could clearly understand what problem did we get and ultimately the solution was produced. Thanks so much for creating a really helpful video without the talks of here and there.

[@uidotdev]

So glad you enjoyed it!

[@aiweekends]

Wow! High quality content!!!!! Excellent video, you kept me hooked all the way. Very nice animations also, it was perfecto

[@uidotdev]

Thank you!

[@hyperupcall]

Funny how Webpack gets that reputation - as a beginner programmer with only a small Electron app under my belt, it literally took a week to get a working Webpack configuration to do what I want (VueJS instead of React). Now, with my current experience, it doesn't seem _that_ bad - only time consuming. Overall, great video! One thing that I think was left out was the mention of Douglas Crockford and Google Maps. Douglas Crockford was one of the earliest people to use JavaScript for serious large apps in production, even before Google Maps. And Google Map really proved to the masses that it was possible to do great things with JavaScript

[@froggologies]

Nice content, dude! It would be great if the next video was about CSS frameworks or libraries. You have done Typescript, React, Next.js, so I am looking forward to it.

[@uidotdev]

Good idea!

[@mayurkumar2127]

Why tailwind css won 😏

[@froggologies]

@@mayurkumar2127 Well, I certainly hope so. But either way, I like to see how he make content out of it.

[@Chris-zt4ol]

There is so much more to Next.js which makes it super awesome. I spent the last week or so to read through the entire documentation because its fascination me so much what great features especially with version 12 it offers and how much attention to detail is put into it.

[@uidotdev]

Agree!

[@kemekenneth]

"If you're really kinky you could pick the webpack docs for your punishment of choice" 😂 Love the storytelling and narration, and the subtle humour.

[@uidotdev]

Thank you!

[@JohnBartmannMusic]

historical storytelling meets tutorial. new fav channel.

[@wlockuz4467]

I think I found a goldmine of channel! Keep up the great work!

[@apresthus87]

NextJS quickly became my go to dev framework for building web apps after giving it a go in a smaller project. I have since ported all my large projects over from vanilla react to NextJS as well. I just love the versatility it gives you and I love essentially having a node server and server rendered pages available whenever I need it. It's so nice to build out API's for my web apps without having to jump back and forth.

[@uidotdev]

Agree. Thanks for watching!

[@smtkumar007]

i am just curious since i am a laravel dev , what does nextjs gives that laravel with vuejs spa doesn't..?

[@apresthus87]

@@smtkumar007 Can't really say since I haven't used laravel (it's a php backend no?) . NextJS is great for those that use a React and NodeJS stack, like myself. And I really like the fact that you can do server rendered, client rendered or inbetween on a page by page basis with ease without the need for an external server or additional dependencies.

[@Light-nn6hn]

@Alexander Presthus could u explain what the *API's for my web app without having to jump back and fourth* part mean? i know what an API is but that sentence made me confused, thank you

[@apresthus87]

​@@Light-nn6hn By that I simply mean that I don't have to have two projects, one React Front end Web app and another one for an Express or Node JS server. Granted, you can include the server in the front end project but for me it's a bit messy, and you still have to host your server somewhere. To use a project of mine as an example- A CMS, all the front end code is divided among pages and components but I can seamlessly work on the back end by using the API routes in next. I have a route for a single post, page, as well as all posts and pages. That API route has access to the Firebase Admin API and can authenticate and verify access with JWT's for example, or simply send back all public pages or posts where applicable and voilla I have a headless CMS working. This flexibility means that I can also consume the api routes within my front end application if I wanted to serve pages statically or have them be server rendered in general. Of course you can do all of this just fine with a dedicated server, but I find it so useful to be able to switch between working server side and client side in a matter of second . Don't know if this aclrified anything at all :P

[@kraavok]

Excellent video! Well thought out and loving the animations to describe your points

[@uidotdev]

Thank you!

[@galaparadi]

i really love content with this kind of format. Keep it up.

[@uidotdev]

Thank you!

[@akashchoudhary8162]

Damn. There was once a time where Apple was supportive of web apps and now there's a time where Apple doesn't let PWAs to be published directly via the App Store.

[@uidotdev]

Sadly true

[@Gaming214-y3g]

Apple killed web apps, instead of making their browser better or solution, there introduced native apps. Remember the popular term, "there's an app for that"? Practically, many web apps has to built a native version and for different platform. Now, let think about the history before web apps, there're desktop app (aka native apps on mobile) and we have to built for different platform, install it and so on. Then came web apps, many native apps migrated to web apps. Then came iPhone and due to the limitation of it's browser, they bring back native apps and every web apps were forced to built native versions and back to the old days, you had to maintain different versions for different platforms, hire different developers, the need to install and so on. PWA or modern web apps were trying to solve this problem, why do we need to built native apps at all (unless it's really the nature or required). Media players or those kind of devices, make sense to have special app built since it has limited user control and was never meant to be a mobile computer. Smartphone on the other hand was totally a different story, it was invented as a mobile computer and a phone in 1 device. In the past, we needed to carry 2 or more devices, a phone , pocket PC and probably a laptop. Anyway, even before PWA, there were many attempts to resolve this like a hybrid app, where you have an app container which render web content. However, everything was messy, no standardization and so on.

[@keent]

it's ironic because most of their apps are WebViews. You can even force to inspect element on the Settings app on macOS

[@thewiirocks]

@@Gaming214-y3g In fairness, the market pretty much forced Apple’s hand. Hackers created an app store before Apple did and many iPhone users were jailbreaking their phone to get it. So Apple introduced an app store long before the hardware was ready for it. (The original iPhone hardware was massively underpowered for anything other than its default apps.)

[@Gaming214-y3g]

@@thewiirocks the irony that users paid premium to a device that they only get a very limited account like a Guest account where they could only use apps. Imagine buying a MacBook and you can only use the browser and the app store. To be fair, without the App store and apps from Apple, many people wouldn't have switch to iPhone. It was the apps that attracted people. Back in the days, we have many better smartphones that have capable browser that could render web especially Facebook, but by having the app it gives the user a much better experience due to the state of web apps back then. Many apps were available in the iPhone like Facebook, WhatsApp and so on and it's a privilege to iPhone because other platform either doesn't have it or needs time to port. Instead of making their browser more capable or solution for web apps, they introduce alternative native app for web which solve their problem but created problems for the rest.

[@rahulmutreja]

The way you presented the whole video was 🤌🏼. It would be great if you could do a next.js vs remix comparison.

[@uidotdev]

Thank you! That's on our radar.

[@boian-inavov]

Next.js is definitely not alone in the static world, but the general concept of pre-packaging static files and just shipping the already processed files is a revolution in page load, speed of development and cost.

[@uidotdev]

Agree. Thanks for watching!

[@itsjustboarsley]

I’m a c++/GoLang backend dev and never touched web stuff. Trying to start with no knowledge of any frameworks was wild so I decided to roll a small one of my own to learn how they work. Now I’m here, and I’m stoked about nextjs

[@daniel29009]

Fantastic work, thank you! Love the way you present historic content. For react, what most people overlook is the fact that is all js, not modified markup or fancy css slang. I value it a lot after years of suffering through jsp world. That's why vue and angular can never compete with react in my eyes.

[@uidotdev]

Agree!

[@udev6707]

@Denis you really need to check NuxtJS, I bet you will love it (kzbin.info/www/bejne/pKDUXo1-ialleck)

[@clarktolosa]

hope u make more of these! loved the visuals

[@uidotdev]

That's our plan. Thanks for watching!

[@create_space812]

this video is epic. thanks for putting this together!

[@uidotdev]

Glad you enjoyed it!

[@mmk-69420]

I don't know why but I can't get out of my head the "*Backbonejs invented the MVC architecture*" joke from the React video of this series. Great video again btw!

[@uidotdev]

😂 You don't know how many people that one line has triggered.

[@andreas_tech]

straight sub. love this graphical / visual approach.

[@uidotdev]

Thank you!

[@JoshuaJMorley]

Your presentation of the evolution of web development and the feature set of next.js is fantastic! I would point out to viewers that the statement "every decade or so a technology comes along that changes how we write software" should be interpreted with a web development lens, next.js wont impact the software disciplines of data engineering, cloud development, game development, embedded etc

[@uidotdev]

That's fair. Sadly, I have to say stupid stuff like that for the KZbin algo. Going into qualifiers like that would be objectively true, but ruin the flow a bit.

[@JoshuaJMorley]

@@uidotdev For sure :) but impeccable content and big props to replying to comments!

[@julianhu]

Best next.js intro video I've ever seen!

[@ManasMadrecha]

What about Nuxt.js? I think the V3 is going to have all Next.js features, plus it's more simple to learn because of Vue. I personally learned Nuxt first, and then Vue, and then javascript.

[@uidotdev]

Nuxt is great too

[@udev6707]

@no1youknowz yeah right, check this video from fireship and you will know NextJS is no way near NuxtJS kzbin.info/www/bejne/pKDUXo1-ialleck)

[@ericknudtson1956]

No thanks

[@denniszenanywhere]

Best presentation of Next JS I've seen. You think Next JS is the best? What do you think of Svelte? Can you do a video on that, too, as Vercel, people behind NextJS, has taken it upon themselves to improve Svelte with Rich Harris. I think it's a great move on Vercel's part.

[@uidotdev]

100% agree. Svelte is on our list to cover.

[@denniszenanywhere]

@@uidotdev Great. Can't wait.

[@mtgshmoopy]

IMO using Vite, TS, and React to create a SPA is the best way to create an enterprise front end application. The features of Next add too much complexity for an enterprise environment (think in terms of personnel, onboarding, that kind of thing). However complexity is always being reduced. Simply migrating from CRA to Vite reduced our overhead by a very noticeable amount, for example. I'm always finding myself returning to Next whenever I want to spin something up as a quick PoC so I'm very much looking forward to its future. Anyone who likes JS, regardless of FE/BE/whatever will like using Next.

[@uidotdev]

Thanks for watching!

[@ayushvyas3401]

I'm relatively newer to web development and as far as my knowledge goes, isn't CSR bad for SEO and even website speed in some cases?

[@professor_ozzy]

@@ayushvyas3401 Correct

[@ayushvyas3401]

@@professor_ozzy hey can't believe this was 5 months back, I went ahead and learnt react after which I completed the MERN stack then moved to next js. It's crazy how much learning is possible if you're dedicated enough

[@professor_ozzy]

@@ayushvyas3401 Oh. Cool! How was your adventure? Do you prefer Back-end or front-end man?

[@MinnoqWV]

A common criticism of development careers is that people often say that it's really difficult to keep up with learning the latest frameworks, technologies, etc. It's not a totally unfair point, but I've always felt that they mostly just keep making life easier! I suppose there's some growing pains along the way, but ultimately I love seeing what new stuff the geniuses have come up with

[@uidotdev]

Totally agree

[@ontheruntonowhere]

They make life easier if you're fortunate to pick the correct (read: has longevity and community support) framework to spend dozens of (typically unpaid) hours learning. But that process of picking becomes quite stressful when there are 1) dozens of frameworks to choose from and everyone is constantly jumping to the next shiny thing, only to abandon it after a single project, leading to 2) lots of legacy dreck that some poor developer (typically me) has to reverse engineer and fix, hopefully with the correct framework this time.

[@riddixdan5572]

I lovethe quality on this video. awesome content.

[@uidotdev]

Thank you!

[@ksato3991]

U really hit it out of the ball park with this one!! If anyone asks me what Next is, I’ll just show them this vid from now on.

[@uidotdev]

That means so much. Thanks for watching!

[@camerakaravan]

Impeccably engaging, loved your content!

[@uidotdev]

Thank you!

[@aayush_karna]

Now this is a quality content.

[@uidotdev]

Thank you!

[@vegedus]

I feel like there's something I'm still misunderstanding about NextJS, because it mostly seems like micro-optimizing to me. My experience is generally that vanilla React is fast "enough" for the most part, as long as you stick to best practices and use memoization appropriately and such. 90% of performance problems I've encountered in my professional life are in the back-end, it seems like a moot point that you can shave a 1/10 off a second off of app load, when there's API requests taking 5 seconds. If you're working with significant amounts of data, any time working on the front-(presuming you're fullstack) is wasted compared to working optimizing SQL queries or setting up caches and what not. There's also other, simpler code splitting tools or Preact for minimizing bundle sizes. I can see NextJS being useful if you're making a surfable mobile app, say a news site, where user retention and attention span is incredibly important, but for the stuff I do professionally, heavy enterprise B2B CRUD apps, it barely seems worth the added complexity. Am I wrong?

[@uidotdev]

Yes :)

[@blueSurfer]

React docs disagree with u

[@johndoejohnnydoe1477]

Not just initial page load . All pages will be of same page load. Too quick.

[@turolretar]

Next makes react bearable at least

[@tytrdev]

Fantastic content. I recently started mentoring my best friend 1:1 (a very serious, structured mentorship) to help him get into app development and software engineering. Early on I told him that one of the most important things is just mindset and perspective. Not just mechanical skills. This includes learning the history of where we are now and how we got here. Just understanding how react let’s you handle state is not enough to go make good software. I’ve consulted on react apps that were the craziest mess of spindly, spiderwebby chaos you can imagine. And I’ve worked with COBOL code bases that were actually quite pleasant (at least once you’ve gotten over the shock of COBOL…). The value Understanding the progression in web history from chaotic jquery state/view complecting to the modern philosophy of views being a function of state, it just can’t be overstated. Just really love these videos because I feel like I can hand them off to my mentees who are still fairly green and they get a massive amount of benefit out of it. Great work here. As an extension to this I think it would be great to see something like this that explores the more theoretical side of things. Like entscheidungsproblem and the Turing/church era. There’s a lot of wisdom to be extrapolated from the history there without getting bogged down by the technical complexity. Sorry I’m ranting. Really just wanted to say top notch content. This context is legitimately helpful for real humans and you are doing great work. Keep it up!

[@uidotdev]

That was a lovely rant to read and I think you're totally right. Thanks for the kind words and suggestions!

[@tombemin]

This is exactly what I needed. Thanks for your great work, your videos are premium quality contents 👏

[@uidotdev]

You're very welcome! Glad it was helpful.

[@sil0_o]

I wanted to sub, and then I've realised I already was.. guess your content is as dope as it used to be when I subbed

[@uidotdev]

❤️

[@nonlinearfruit8065]

Super helpful. Thank you! A piece of technical feedback: It would be super helpful to share links to the source material for further research. Techlore does this with markdown file in a git repo (which I love) but even just in the video description would be great. Again, great video. The effort shows in the historical sources. Thank you and thank you for siting sources on screen, that is great!

[@uidotdev]

Great suggestion!

[@AustinShelby]

Great video and the animations are sick!

[@uidotdev]

Thanks a ton!

[@pm71241]

Still ... as a backend developer, I'm really happy I haven't spent too much time on Frontend before the age of css grid/flexbox, web workers, indexedDB and WebAssembly

[@ankk98]

Your clarity of thought is impressive

[@kayode8428]

Excellent video as always. Love this channel. Keep it up.

[@uidotdev]

Thank you!

[@thanatosor]

The React part just got me. As a backend, engine dev, hoping into React Native / Ionic really confused me a lot by their documents and the mess I need to put in my brain before it really do something useful.

[@uidotdev]

Thanks for watching!

[@TJ-hs1qm]

must say as a BE dev React is the first and only js "framework" that ever made sense to me. And I've seen them all. ps: I've been in software development since the ancient times of Mosaic and Slashdot ^^

[@cas818028]

Also comes with vendor locking out of the box

[@nyashachiroro2531]

Lovely video. I like NextJS. I'm also happy Remix is improving on it.

[@uidotdev]

Remix is great too. Thanks for watching!

[@kendedetar]

this video is extremely well made! I really appreciate you taking the time to make this.

[@uidotdev]

So glad it was helpful. Thanks for watching!

[@SpicyMelonYT]

Masterful video My dude. That was amazing. I make video games with things like unity and unreal, so none of this stuff really matters to me. And yet I was fully engaged in the video the entire time. So interesting and distilled. Nice Job loved it!

[@uidotdev]

That means so much. Thank you for watching!

[@SpicyMelonYT]

@@uidotdev my pleasure

[@Noah-vm8id]

NextJS is love, thank you Vercel 🙏

[@DB-zv5ro]

I've watched some of your videos, and love the presentation and animation. If it's something you're comfortable sharing, could you share what tool you used to build the animations in the video? For example, like the ones at 10:05 (animation on the left, code on right)

[@junaiderade3975]

this is one of the best web dev videos i've ever seen.

[@thenightguy6816]

Remix provides good competition so that Next keeps up with it

[@uidotdev]

Remix is great too

[@sidneylc28]

This is top notch quality, I'm really glad I found your channel. I know you are into js, but can you make a video about the story of c# from the beginning to what it is now? From similarity to Java to maui and so on

[@uidotdev]

Thank you Sidney! We definitely plan on exploring things outside of JS, but it'll be a while since it's not what we're familiar with.

[@lemontec]

In the late 2010s I switch from frontend work to backend work because I just couldn’t stand it anymore. 2 months ago I started learning Next with no background in SPAs or React and it has brought back the joy of web development to me. This video is more than a year old now and holds up well but there have already been many more great innovations added to Next like App Router, React Server Components, Streaming or Server Actions

[@bopon4090]

I have so many things to learn from 5his channel. Thank god i found this channel. ❤️❤️❤️

[@uidotdev]

Welcome ❤️

[@pratikmilind-1889]

Content was so amazing even as a fresher in this technology i can clearly understand where are frameworks are holding nowadays .

[@mohey2222]

Maybe make a video on Remix vs Next.js? I'm on the fence for now and would like to know what you think.

[@uidotdev]

It's on our list

[@Alan-lb8ef]

The ending implies Tyler's leaning towards Next. Kent won't be a happy koala 😂

[@uidotdev]

@@Alan-lb8ef I really do like Remix as well. Kent and Ryan are good friends of mine.

[@Alan-lb8ef]

@@uidotdev Yeah, I'm a fan of Kent and Remix as well. I'm looking forward to getting around to playing with Remix more and I'm rooting for it to be just as adopted as Next is or more. That remix vs next blog seems to have rubbed people the wrong way online though. 😅

[@huxnwebdev]

Awesome Content, As Always 🤘

[@uidotdev]

❤

[@ljuglampa]

Good job! Looking forward to more web history packaged like this. ❤️

[@uidotdev]

Thank you!

[@nilfux]

This is a near perfect breakdown. Especially the evolution and how Next has combined all of the findings of that evolution into a holistic solution. The parts don't solve everything, but together it's the near perfect stack. Can you do a video on NestJS? I find it interesting how I'm able to bring Java people in my org over to my team and they can pick up NestJS almost immediately -- since it's very Spring bootlike.

[@uidotdev]

So glad you found it helpful. The hard part about videos like this is you really need a fairly deep understanding/history of the tech to make it work. I'm not too familiar with NestJS so I'm afraid I can't add much to that discussion (at least yet).

[@casper0165ful]

Cool video. Love the way to clearly explain it and put it into perspective

[@uidotdev]

Thank you!

[@Altroo]

Best history video lol, keep it up. Can't wait for a react native same style video