⚡️ The Remix Way: how the framework’s new approach changes engineering thinking
The philosophy of Remix 3: modular libraries, interfaces as contracts and native web primitives.
In a new post, Sergio Xalambri explores the new philosophy of Remix 3 in “The Remix Way”. The key message is that Remix is no longer trying to be yet another wrapper with a create-app button. Instead, the team offers a set of modular libraries with zero dependencies and a strong focus on native web standards.
The author decided to rewrite his blog using this new stack to test the concept in practice. Here are the insights he came away with:
- Interfaces as contracts: Remix provides not just utility functions, but flexible contracts that can be extended and recomposed for your needs. This approach resonated so strongly with the author that he reconsidered his approach to the architecture of his own libraries.
- Custom styling: Building on this way of thinking, he created his own styling library, implementing a Tailwind-like approach directly within the Remix ecosystem.
- Native web primitives: Since Remix leans heavily on web-platform standards, the author followed the same principle: he completely abandoned heavyweight i18n libraries and wrote a lightweight implementation based on the specification for the upcoming
Intl.MessageFormat.
The article’s main takeaway: “I stopped simply using Remix to build applications: I started building applications the Remix way.” It is a great example of how an architectural shift in a tool changes the very approach to writing code and designing systems.