This is me, learning JS at the moment and looking into technologies and frameworks to look for. It is quite overwhelming, but everyday I learn something new. I'll get there eventually.
react-router has been a dumpster fire for ages. They constantly released new major versions with breaking changes, and by the time you got migrated over they had released a new major version with more breaking changes. I’m glad to see it go.
Figuratively, in the last 10 years, all of web dev took a ride to the client and now back to the server. I am not confident though that our tools are now 10 years better than what we had 10 years ago. I think the biggest one that I feel day to day is actually just Tailwind, which is pretty orthogonal to that whole development. And Browsers got a lot better, too.
As someone newer to learning this, is it more worthwhile to focus on React or to focus on Next for the eventual job search this summer? I know the main difference is client vs server obviously but I see more Next tutorials than React specific ones these days
@@wojtek5693 I mean yeah maybe. It has created a hole bunch of issues to deal with. Maybe in the end it will be better. But not having to go on this wild wild ride would also have been quite nice
Great video, thanks theo ! One thing i never understand, why force this server-first behaviour? Splitted SPA has stil it usage primarily in dashboard websites, where server rendering stuff does not bring much to the table and forces the developers to setup a next server to deploy a dashboard website, not to mention the mismatch errors in highly dynamic pages and forcing on cookie based authentication for SSR to work. (SSR doesn't work with JWT for example) With SPA it could be easily be hosted on a simple http server to serve static files. I understand the benefit of the server model but let me choose when i want Server component, SSR or SPA. ALL I'm saying is that these decisions shouldn't be taken for developers, let them opt in for every page they want. IMO this is one of the primary reasons Remix got the attention it deserved, it filled a gap created with deprecation of CRA. This is the primary reason i think folks at nuxt approached these problems really carefully and delivered the best of both worlds with developers in control, sadly it is not as advertised as other "fancy" things in other communities.
WTF are they talking about? This has already been available with Vite without Remix for many months. It's incredibly easy to do with minimal configurations. I don't get what it is they're trying to take credit for, they didn't actually do anything new.
@@ra-dro they're talking about Remix the web framework. Check it out because it's genuinely interesting the way they approach web app development within a single file for frontend and backend, and their routing is convention over config.
I was hyped... for a few days. Then realized that form-based actions are untyped (unlike what we currently have at work with Zodios), that there's no adequate monorepo example, that docs are very shallow. Not sure if it's worth the hype, at least not with React at the core. SvelteKit and SolidStart look more interesting IMO.
I would rather use blazor , at this point js world is so messy that even intermediate developers wouldn't have a clue the nice thing about lazor is that you can use when ever needed both in the frontend and backend (polyglot programming) but still need slightly better DX and community support ! , ( did I mentioned you can warp react components ? )
React Router when you use JS and don't care about putting routes path in any const or strict architecture way: Welcome traveller! React Router when you trying use it with TS with strict routing: *Goes brrrrrrrrrr*
7 месяцев назад
Your title says "the end", you description says "finally dead", but then you say that the project might be merging, which means that React Router is very much here to stay. Do you… want it gone for some reason? Has the React community been complaining about its existence? Why did you think it was important to announce this as a fact based on a single thread, and then proceed to not talk about the subject anymore?
Funny enough, I actually liked making my Webpack configs. It was awesome to use openly available plugins to optimize my own code! However, I love the way things are going with things like Parcel: obfuscate the build details and get the best optimizations out of the box.
I would love to see a video on why you think Next.js with app router has a better data loading + mutation story than Remix. Because imo Remix is miles better than what I see in Next.
Yeah as much as I'm a Remix fan boy, I find data loading being tied to components rather than routes a more intuitive mental model - but I suppose that's because my brain has been so infected by React SPAs and their data loading patterns over the years!
Another reason i use Angular. From v2 to v17 we always use the included router module unlike react where you can use react router (which isn't even made by the react team), vite, or routers built into next js, gatsby. Its a nightmare, where is the consistency?
TLDR: Next version of "React Router" may or may not merge/flow into "Remix Router", hence the install package naming might change for the end users (devs), depending on the decision. If you are so panic with your comment, you just don't watch the first 1min of the video. Well, as least you know the news because of the clickbait, better than later panic about why React Router never got updated (if they change to remix router), and asked some random questions in github repo or reddit or twitter or whatever, and blame the maintainers.
Thanks Theo - this video is perfect timing for me. I'm just about to embark on starting a new React project for work which is going to be pure SPA (with a C# .NET on the server side). I've been debating between using NextJS and Vite for a while now. Perhaps Remix with its SPA mode along with Vite would be the best option now ?
Nuxt works identical to old next in this, but uses Vite now. Generally speaking, the innovation on the Nuxt side is in the dev tools and features, not the technical implementations
Is that Vite is already have Remix when you initialize npx create-vite-app? What's gonna be a difference if Remix themselves turn the Vanila Remix to Vite?
I have a question. In next js app router, what is the best way to set default route example default route of my site should be '/dashboard' instead of '/'
Web dev is a hot mess! It all needs to be razed to the ground and started anew. HTML, CSS and JavaScript needs to be dumped. Replaced with what I don’t know maybe something grounded in web assembly but this video is proof to me that it all needs a major overhaul. Otherwise this churn is just going to get worse.
bro i don't get why there is so much shit always changing in the web dev world when like 99% of people use 3 websites 99% of the time they browse. and they fucking browse on their phones!
Will check this later but I love to see how Vue is consistent on it's upgrades without having breaking changes. I have the feeling Reacts gets more and more like Angular by all the latest updates that it introduces?
@@KevinVandyTech I am talking about all the changes that lately happend to React that devs are complaining about that resolved into rewriting existing code (mostly). Not sure which breaking Changes you mean on Vue 3 but I can tell you it's by far simpler, even you can get into complex syntax like on React, too. But the question is, why would do that freely if you can get the same result with less hassle? Not gonna protect Vue over React or anything, just saying what I noticed from most of the devs out there. But still prefer Vue over React.
Very informative, Hey Theo do u really want to know why i follow your content? I'm 29y Fullstack dev (Node+React) since late 2018 Now days Sr. Software Engineer working remotely with American contracts I WANT TO KNOW IF MY BOOK VALUE (ALL THE SHIT I'VE LEARNED SO FAR) IS STILL HIGH IN THE GOD DAMNED MARKET! simply as that, nothing more, nothing less
you have uploaded 3 videos already saying react router ended already, that is confusing for beginners and people watching you trying to improve. I tried other options you share and just threw them away for the basic most used react router. Seems like the focus is merely on the tools rather on the products.
I have never understood the need for routing and state management libraries. Those have always been easy to write by hand and have been a minuscule fraction of my projects. I feel like I'm taking crazy pills.
Yes, webpack sucks and doesn't suck at the same time. Because I remember all those years ago that it did the job and am grateful for it even if it's not the best anymore.
Funny how a washed up RU-vidr can have a better grade then you on Social Blade. I am also offended that Social Blade thinks he can have 16.5M views in the last month while you, God himself, the best creator ever, said he only got 30k views on his videos.
React router has been going in the wrong direction anyway. They introduced all these data fetching hooks and try to do way too much. It should've sticked to just being a router. But then again react router is probably the most amateuristic/incompetent library that somehow is still popular. The amount of complete rewrites over the year is staggering.
