riot VS Svelte

These articles form a series focusing on RiotJS paired with BeerCSS, designed to guide you through creating components and mastering best practices for building production-ready applications. I assume you have a foundational understanding of Riot; however, feel free to refer to the documentation if needed: https://riot.js.org/documentation/

This article covers how to create an Riot input component, using the Material Design CSS BeerCSS. Before starting, make sure you have a base application running, or read my previous article Setup Riot + BeerCSS + Vite.

However, Riot is my first choice when creating a front-end, here is why:

Riot.js is designed to be lightweight and easy to learn, making it a good choice for developers who are familiar with HTML and JavaScript — without requiring them to learn the rigors of coding with a specific framework. Riot.js emphasizes simplicity, performance, and modularity, its ecosystem allows for easy integration of third-party libraries and components, making it suitable for both small-scale and large-scale projects.

how about getting a hold of your sanity and allowing yourself a few hours to learn https://riot.js.org/ - almost no learning curve, only pure awesomeness. even if you won't use it in the enterprise (because policies, bla bla), it is still worth knowing things can be done differently - in a good way.

In theory, “de-frameworking yourself” is cool, but in practice, it’ll just lead to you building what effectively is your own ad hoc less battle-tested, probably less secure, and likely less performant de facto framework.

I’m not convinced it’s worth it.

If you want something à la KISS[0][0], just use Svelte/SvelteKit[1][1].

Nowadays, the primary exception I see to my point here is if your goal is to better understand what’s going on under the hood of many libraries and frameworks.

[0]: https://en.wikipedia.org/wiki/KISS_principle

[1]: https://svelte.dev

When I teased this series on LinkedIn, one comment quipped that Vue’s been around since 2014—“you should’ve learned it by now!”—and they’re not wrong. The JS ecosystem churns out UI libraries like Svelte, Solid, RxJS, and more, each pushing reactivity forward. React’s ubiquity made it my go-to for stability and career momentum. Now I’m ready to revisit new patterns and sharpen my tool-belt.

What is the advantage over Svelte (https://svelte.dev/)? Especially since Svelte is already established and has an ecosystem.

At Project Au Lait, we are developing and publishing an open-source asset called SVQK, which combines Svelte (Frontend) and Quarkus (Backend) for web application development. The asset includes automated testing tools and source code generation tools. This article introduces an overview of SVQK. (For instructions on how to use SVQK, refer to the Quick Start.)

Yes, Solid is very fast, but Svelte's Signals implementation seems to be even more performant. [0]

I just loved the simplicity of using $: for deriveds and effects in Svelte 3 and 4. But after building a correlation matrix [1] and a work project with Svelte 5, I have to say that I really like it.

[0] https://github.com/sveltejs/svelte/discussions/13277

[1] https://covary.xyz