The End Of React Router

preview_player
Показать описание
React Router was an essential part of the success of React. It is finally dead. Let's talk about why, including a bunch of Remix chatter.

SOURCES

S/O Ph4se0n3 for the awesome edit 🙏
Рекомендации по теме
Комментарии
Автор

I'm not sure how to React to this.

AquaQuokka
Автор

Imagine showing this madness to someone who is unfamiliar with or new to webdev

william
Автор

The final breaking change. They've been preparing us for this for years

rubberdork
Автор

it is so relieving that i don't know any of what this video is about

Sntia
Автор

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.

catalystcorp
Автор

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.

roodood
Автор

Damn guys are you still in 2014 with these 'first, seconds...' ridiculous. I'm 8th btw

romanr
Автор

What if turbopack and rolldown team combines??? They are trying to build same thing right?? In the same language

jitxhere
Автор

Funny i still don't see how this replace React router Dom. Worse is nextjs looks more like a mess in a dynamic large scale.

muchirajunior
Автор

I don't think "paid template for react router" is a fair way to talk about Remix, even very early versions

JLarky
Автор

In angular, we only use angular routing and happily live after

LailahaillahChannel
Автор

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.

destroyonload
Автор

I wish react had a router of their own like these libraries and we didn't need another imports for basic functionality... great news nonetheless

cetincetindag
Автор

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.

Saeid-Za
Автор

Bundler wars is true. It hurt to see so many tools doing the exact same thing. JavaScript devs are wild

hannad
Автор

Got clickbaited but learnt about JS bundlers so its not so bad

neofox
Автор

Men I don’t know why I didn’t stick to Flutter

alexandrodisla
Автор

oop. Post React Conf it seems like it's the other way around 😬

jamjamatt
Автор

The thing I hate about you is the bait titles you put. You literally put "_ is Dead"

eikyoutube
Автор

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?