riot VS Preact

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.

Riot.js prides itself as a light and simple UI library that helps developers hit the ground running when creating elegant UIs for their applications.

Thanks! Glad you like it. I'm the original author of Riot (https://riot.js.org/) so that's the style of frontend development I'm most comfortable with. We're using our own flavour of the library, which has the original super-mimimalistic feel on it.

You see, there is a JS framework, called Preact. It's an alternative to React with the same API. And there is a very interesting statement on its official page.

In this article, we will create a simple Chrome extension, that will be responsible for displaying recent top posts from DEV Community. For this, we will use Preact bootstrapped with Vite build tool.

Bear in mind that this is still under review by the Preact team but if you need it desperately like us, feel free try out the preact-async package on npm. I'm hoping that Preact team will accept this change and get it into the main package.

[2] "preact-compat adds somewhere around 2kb to your bundle size, but has the advantage of supporting the vast majority of existing React modules you might find on npm" https://preactjs.com/guide/v8/switching-to-preact/

Not sure what exactly you would like to replicate but frontend is done with Preact https://preactjs.com/ . Hope that helps.

I've been doing some web programming using preact these last weeks and one of the things that impressed the most was the way logic and UI are split in code. When doing functional components this is specially explicit. Your function returns whatever should be displayed by the component and receives a props object containing all the information the components need to render. A component rerenders when some of its props are changed, either because an external component made changes or in response to an event.

Preact is a "Fast 3kB alternative to React with the same modern API". It's smaller than React but shares most of it's features (Hooks, Context), so you can write normal React code but benefit from better performance.

A few months ago, I wrote an article based on optimizing react loading time, and most of the reader's comments were to try Preact to get default optimization. So I decided to try preact with the same app used for the previous article. Let's first get an intro about Preact.

For a long time I heard people complaining that React & ReactDOM has a huge size, and everyone recommended to use Preact instead.

I decided to take his process and methodology and apply it in addition to Preact, React, and Solid. So let's begin.