redux-rs VS solid-site

From the first paragraph:

> ... Architectures that work well in other languages generally don’t adapt well to Rust, mostly because they rely on shared mutable state and that is not idiomatic Rust, to put it mildly. ...

The author doesn't mention Redux (the architecture), which is surprising. There are three principles[1]:

1. The global state of your application is stored in an object tree within a single store.

2. The only way to change the state is to emit an action, an object describing what happened.

3. Changes are made with pure functions.

In other words, the components of an application never mutate the state tree directly. Rather, they emit actions which re-generates the state tree without mutation.

This style of state management is compatible with Rust's ownership model. The emphasis on pure functions means that it's not necessary for your application to hold multiple mutable references, which I'm guessing underlies the "generally don't adapt well to Rust" part of the claim.

[1] https://redux.js.org/understanding/thinking-in-redux/three-p...

[2] https://github.com/jaredonline/redux-rs

SolidJS is a popular and open-source declarative JavaScript library that empowers reactive UI interfaces for the web that ensures a performant benchmark, leverages the flexibility of JSX and also provides support for TypeScript, Astro, and Vite.

In 2023 there are a wealth of developer options for front-end: React, Vue, Svelte, Solid and many more.

You may or may not yet have heard about Solid Start, which is the much anticipated upcoming meta framework for Solid.js currently being in beta.

SolidJS is a powerful, pragmatic and productive JavaScript library for building user interfaces with simple and performant reactivity. It stands on the shoulders of giants, particularly React and Knockout. If you've developed with React Functional Components and Hooks before, Solid will feel very natural because it follows the same philosophy as React, with unidirectional data flow, read/write segregation, and immutable interfaces.

Things like Solid (https://www.solidjs.com/) also have no virtual DOM, and the improves are in higher ceiling for performance, lower memory usage, simpler DX (components are not re-executed, there aren't any dependency arrays everywhere), easy high performance (no useRef this and useRef that to make things fast, no useCallback, no React.memo, these things are just obsolete).

Made with: - Windblade (my own version of Tailwind) - Solid JS - Vite

SolidJS

For the time being, this is how I approach web development on pretty much every project I have “architectural control” over. That’s how I worked with Solid.js and Tailwind CSS for the past 2 years. That’s how Vrite is being built. Has worked pretty well so far…

SolidJS (They've started building the SolidStart and I want to give it a try)