React Router V7

I'm excited about the upcoming release of React Router v7. At first, I was concerned because I have become very fond of Remix and worried that the release of React Router v7 would mean the end of Remix. However, after the announcement, I now know that the features I've come to enjoy about Remix are moving to React Router v7. This transition means that Remix's awesome features have a better chance of gaining traction in a space dominated by NextJS.

The developer experience with Remix is one of the best. I have been creating websites and web applications for almost 30 years in various languages (Perl, PHP, .NET, ActionScript, Ruby, Python, Java, JavaScript), and I have never been more excited about a technology than I am about Remix. Over the past two years, I've worked extensively with NextJS and Remix, including a complete rewrite of a Drupal/MySQL website to Remix and Postgres.

Remix developers have simplified the complexity the JavaScript community has introduced by trying to make SPAs full web applications. They have focused on using HTML conventions as they were intended. Due to loader and action functions, there is no more duplicate validation of forms and accessing private keys for secure external API calls is trivial to implement.

The benefits of Remix extend beyond loaders and actions. We also get an excellent routing system, allowing an intelligent mapping of URLs to code. While I may have over a hundred files, I can look at a URL and jump directly to the code. URLs are great containers of state and are ideal for sharing extensively filtered data. It's a smart decision to use the URL as intended and makes working with URL variables a breeze.

I hope that by integrating Remix features into the already accepted React Router, more developers will take a look and realize the benefits of incorporating React Router v7 into their projects and am excited to see the impact it will have on the JavaScript community.