Our great sponsors
-
rusty-css
a solution to create and export css styles in a familiar way, but without leaving the rust syntax. You can access and manipulate every value you define on an individual basis.
-
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.
-
-
-
-
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.
-
-
I think it's pretty epic. It's kinda slow to compile. You could try it out in my little abandoned editor project: https://github.com/DavidCks/Judit
I also built a css-in-rust crate: https://github.com/DavidCks/rusty-css That one is actually pretty nice to use and fully tested.
I wrote an app recently with an Actix API backend and a Yew frontend. I didn't enjoy Yew too much. Loading data from the backend seemed to require too much boilerplate. I'm now using Sveltekit and TypeScript for my frontend because I can get something together much faster and with less code. It doesn't give me the confidence of robustness I get with a Rust app but the backend is still Rust so that's good.
You can also check out Dioxus for an alternative Rust WASM framework. I've heard a lot of good things about it.
I've instead been using leptos. I find it's less boiler plate, and plays very nicely with async since the signals are Copy. The "fine grained" reactive model is a lot easier for me to wrap my head around, and leads to better performance. In the JS framework benchmark, leptos is quite competitive with the other top JS frameworks (Dioxus is right behind too!)
Future opportunities - This one's tougher to speak to since leptos is new on the block. I think it's worth exploring leptos (or sycamore?) just to learn about fine-grained reactivity, and comparing how it works compared to a traditional react model. But to me the ecosystem around leptos is promising, with tools like cargo-letpos, leptosfmt, and more, it seems the community is stepping up to help fill some gaps.
Future opportunities - This one's tougher to speak to since leptos is new on the block. I think it's worth exploring leptos (or sycamore?) just to learn about fine-grained reactivity, and comparing how it works compared to a traditional react model. But to me the ecosystem around leptos is promising, with tools like cargo-letpos, leptosfmt, and more, it seems the community is stepping up to help fill some gaps.
For instance: say you want to use leaflet JS to build a map, besides from a static script import, there isn't a great way to bridge that gap. If you need to interact with an external module in some way (i.e, putting markers on a map), then you're in for a bit of a painful time.
I tried my first project with yew as frontend. And my experience was after some time similar to the already mentioned ones: It is a little more to take on than I actually wanted. And some things were not straightforward to achieve. I switched to sycamore for the other projects now and I am much more satisfied (but this could also be since I have some more experience in the Rust ecosystem by now). Changing from yew to sycamore was pretty easy and I can achieve most of the tasks with less code.
I tried my first project with yew as frontend. And my experience was after some time similar to the already mentioned ones: It is a little more to take on than I actually wanted. And some things were not straightforward to achieve. I switched to sycamore for the other projects now and I am much more satisfied (but this could also be since I have some more experience in the Rust ecosystem by now). Changing from yew to sycamore was pretty easy and I can achieve most of the tasks with less code.