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!
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!
This is incredibly good. I think it's the first time ever that I took notes on a RU-vid 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
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!
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!
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
@@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!
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.
I really like your videos, especially your most recent ones, which are more like storytelling. I feel like the programming videos on RU-vid 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
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!
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!
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!!
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!
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!
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.
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.
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.
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.
@@user-cu4bk2gm6q 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.)
@@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.
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 !!
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.
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 !
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.
@@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 😁
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 🌸
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
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.
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.
@@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
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.
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
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.
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 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!
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..
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.
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).
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
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!
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)
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
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.
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
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
Nice video, sums up the core ideas like they were. Though, you make it seem like it was an overnight revolution 😁 Also Vercel's platform makes a big part of the story with all the integrations and things that were previously hard to implement with a small dev team. (in my biased opinion)
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.
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.
@no1youknowz yeah right, check this video from fireship and you will know NextJS is no way near NuxtJS ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-noq-ZHTD2Cg.html)
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
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.
@@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.
@@smtkumar007 Laravel is a more complete framework for backend than nextjs intends to be. Middlewares are stronger in laravel, nextjs doesn't come with out of the box websockets implementation and such. Nextjs can be used with laravel as a front end framework. It gives you the ability to prerender pages, deliver them staticaly and it has its own routing solution and that allows you to use laravel's routes only for the APIs it exposes. So you don't need to, necessarily, look at nextjs as a competitor to laravel. Even in laravels documentation, nextjs is already listed as one of the most common ways to create UI for laravel. But nextjs also brings the ability to create APIs and have middlewares albeit those are way less powerful and opinionated than laravel's. There are times when you'll want to use nextjs with laravel and times when it is best to use it alone. Applications that don't need websockets and communicate mainly through REST APis are easily and quickly developed through nextjs without bringing a backend framework to supplement the areas where nextjs lacks. The one js framework, which could be considered a "competitor" to laravel, is NestJs.(notice the 'S' instead of an 'X') NeXt, on the other hand, fits very well with laravel as an extra framework. In laravel's ecosystem, it would be a competition to Inertia+React/Vue adapters. But Next brings possibilities that Inertia simply doesn't have for now.
@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
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!
Hey, I love the series and I have a suggestion. Yesterday, I signed the contract for my first job in IT and in general, and it seems that I'm required to use Linux terminal for better programming and install WSL, it may not apply specifically to js, but to programming in general, but my idea for the video is "Why Linux won?"
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.
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).
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.
@@DoctorSoulis 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
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?
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!
