This story is unavailable.

Lol. I actually saw it a few weeks ago. It was unfortunate for both of us to have the same name. Mine is being renamed Rudy by the way. Not because of that name similarities. Honestly there are so many graveyard attempts at this that I never thought Redux-First-RoutING would see the light of day.

Unfortunately he’s doing the Redux Little Router way, and you already know the conclusions I’ve drawn about that. All action types are basically the equivalent of PUSH. That’s not to mention Rudy has an exhaustive feature list. I hate having to say this sorta stuff cuz I know he and we all have put a lot of work into this stuff.

Besides the long feature list OF THINGS YOU NEED, Rudy has a lot of nuances in the implementation that have been thought through and rewritten over 8 months. The project is literally 2 months of 70 hour weeks worth of work. I’ve tried many different things and synthesized it to the perfect combination. For example RLR and Redux-First-RouTING likely dispatch actions before URL changes and then when a URL changes dispatch an action. That little inconsistency has possibility to cause u problems. Mine always results in the URL changed first, and then the state changed. This solves problems specifically related to Scroll Restoration.

Next week’s code splitting and chunk/thunk prefecthing capabilities in conjunction with my “Universal” family of packages are going to be big for Rudy. Everything is done nicely in a decoupled way, which is the draw of using this stuff over Next.js. Frameworks are bad. Plain and simple. Maybe not always, but when React and Webpack get the level of abstraction low yet powerful enough it removes the need for frameworks on top. Or another way to put it: With tools like Universal + Rudy, a framework better bring a lot more than Next.js. Rudy + Universal offers their proclaimed core feature with far more flexibility.

Anyway, I hope to collab with anyone who’s invested the time into this problem. Join me at Redux First Router.