Our great sponsors
-
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
-
sauron
A versatile web framework and library for building client-side and server-side web applications
-
-
-
-
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
-
tangram
Discontinued Tangram makes it easy for programmers to train, deploy, and monitor machine learning models.
-
-
-
SaaSHub
SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives
There are two steps there: (1) rust-rdom working enough to be used by Yew, and (2) SSR support built out in Yew utilizing rust-rdom. Part (2) is pretty far away, but (1) is probably about halfway there. I think a more realistic use-case for the library is Sycamore which is much earlier and simpler than Yew. Sycamore support has a tracking issue here: https://github.com/rust-rdom/rust-rdom/issues/15
I used both yew and seed, but the svg support is lacking. Both framework don't render svg elements correctly. As I'm the author of svgbob[0], which heavily uses svg. I wasn't satisfied with both of the frameworks, So I created sauron web framework and I was quite happy with the result. Not only I can do an server side rendering for svgbob[0], I can also write a text-editor[1] with it and achieve a ~15ms typing latency.
I've been using it in production for svgbob. There have been a lot of breaking changes for the past month, but things are starting to stabilize[0] in the 0.43.x release. Hopefully the version stays at 0.43.x and no more breaking changes, due to using better, appropriate or more descriptive names in Struct and functions.
[0]: https://github.com/ivanceras/sauron/blob/master/Changelog.md
Rocket is the most promising up-and-comer I know about: https://rocket.rs/
Iron and Actix are the more stable but more complicated ones
Digging up the topic, I also found that new framework https://github.com/tokio-rs/axum, which already seems to be popular.
Sentry is rewriting some of their libs from Actix to Axum: https://github.com/getsentry/symbolicator/commit/b6ef7cb00b7...
Digging up the topic, I also found that new framework https://github.com/tokio-rs/axum, which already seems to be popular.
Sentry is rewriting some of their libs from Actix to Axum: https://github.com/getsentry/symbolicator/commit/b6ef7cb00b7...
At one point I prototyped a wasm framework inspired by Solid[1]. The results were very promising—an implementation of js-framework-benchmark was 41KB (18KB gzipped), and perforrmance was close to vanillajs. The developer ergonomics were definitely lacking, though.
Benchmark results (look for _cope_)[2][3]
I definitely think whatever happens over the next few years, VDOMs are on their way out.
[1]: https://github.com/whatisaphone/cope/blob/master/crates/js-f...
We chose to use Rust instead of TypeScript for the front end of https://github.com/tangramdotdev/tangram.
This allows us to:
* Share code with our server written in Rust.
I should add that we wrote a crate called pinwheel that uses futures-signals for fine-grained reactivity, uses the builder pattern to avoid macros entirely, and supports server rendering:
Sycamore looks interesting, though it needs some more ergonomic improvements before it becomes more widely usable.
Very very recently some do, and they aren't amazing. I'm not even sure Firefox 93 is officially released yet? https://caniuse.com/?search=datetime-local
WASM is for when you need serious client side crunch power, like running a 3D game. If all you're doing is manipulating the DOM, it's overkill.
For ordinary web sites, the other extreme, DaisyUI, a CSS-only system, seems useful.