sycamore VS dioxus

Perseus is a fast frontend web development framework for Rust with built-in support for reactivity using Sycamore, server-side rendering, and much more. Sycamore is a frontend library that allows you to build interactive user interfaces with Rust. I’d say that Perseus is to Sycamore as Next.js is to React, so it’ll be helpful for you to have a fair understanding of Sycamore before jumping into using Perseus — although it’s not necessary to follow along in this article.

Now, I considered whether to spend more time fixing everything that now failed in sycamore 0.9. But there are major changes ahead which would require yet another major refactoring, to the point where I am not sure whether it would not be more of a rewrite than a refactoring, given my previous experiences with sycamore.

Sycamore.

Sycamore, Yew, or Seed if you want a full-stack solution. (Or Leptos if you want something that's faster but less mature.)

There are others, like Sycamore, similar story as Leptos but imo Leptos is (currently) more ergonomic.

Sycamore is a reactive library for creating web apps in Rust and WebAssembly. https://github.com/sycamore-rs/sycamore

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.

If you want to do fullstack/SPA stuff, check out Sycamore, Seed, and Yew.

If you want to do front-end SPA development, take a look at Yew, Seed, or Sycamore.

I have written a front-end (website) application in Rust that is used internally in production. I wouldn't recommend to use something like sycamore, leptos, dioxus, yew for you next puplic web-app now but i can absolutely see how this is used in the future as those libs mature.

Yes, Sciter is definitely pretty close.

We think we can do better CSS support. Sciter has good CSS2 layout support, but only has it's own proprietary equivalent to Flexbox. Our CSS2 support is currently pretty patchy, but we have good Flexbox and CSS Grid support. We also have full support for things like media queries and css variables which I don't believe Sciter supports.

Regarding "just disable the JS":

You can, but then you won't have scripting support. Blitz still has scripting support without JS using https://github.com/DioxusLabs/dioxus which is a react-like UI framework but in Rust.

Related: Dioxus

> Dioxus is a Rust library for building apps that run on desktop, web, mobile, and more.

https://dioxuslabs.com

(Dioxus uses Tauri)

There's also Tauri which https://dioxuslabs.com/ uses.

Dioxus Labs (http://dioxuslabs.com) | Founding Rust Engineer | San Francisco | in-person | Full-time | 125-150k | 0.5-3% equity

I'm Jonathan, the creator of Dioxus (YC S23). Dioxus is a popular crossplatform GUI library for Rust that, imo, is the easiest way to ship apps that are beautiful, fast, and robust.

Dioxus is quite popular, almost 20k stars on GitHub, and we recently raised a sizable seed round from "top vcs." We have a lot of exciting projects on the horizon:

- in-place binary patching for rust hotreloading (http://github.com/jkelleyrtp/ipbp)

- a WGPU powered HTML/CSS renderer (http://github.com/dioxusLabs/blitz)

- experiments with LLM-based component generation (http://github.com/dioxusLabs/dioxus-ai)

- upcoming mobile tooling

- TUI-based devtools for a ruby-on-rail like experience

- a deploy platform for web/desktop/mobile/backend and all the fun that entails...

I'm looking for a founding systems engineer passionate about Rust, WASM, apps, the web, compilers, linkers, and devex - basically someone who's not afraid of anything. Dioxus is a very lean organization and we've been able to move so quickly since we keep our team small and high trust. No annoying standups or corporate bureaucracy. If you want to contribute to OSS, move the needle, and work in a startup that's closer to deeptech with hard problems, this role is for you.

I'm specifically looking for people who are excited by this space and doing this type of work. If you're just looking for a job then this probably isn't the right role for you.

Apply on our yc page or are reach me directly at jon at dioxuslabs dot com

https://www.ycombinator.com/companies/dioxus-labs/jobs/dRPOo...

We have a web components example here: https://github.com/DioxusLabs/dioxus/blob/fd21c971038840130f...

Everything should work like normal except: attributes are not typed, custom event listeners must be implemented with web-sys

I think something like https://dioxuslabs.com could deliver native, cross platform apps and win back mobile.

While we took an in-depth look at Dioxus in this tutorial, there is still so much to learn. Luckily, Dioxus provides detailed documentation with references and cookbooks to guide developers. Make sure you check it out, and feel free to comment below with any questions.

You can probably imagine the challenges of integrating such a system in a robust way that does a good job and improves on the status quo. We felt like the Tauri implementation worked well for Tauri apps. But there’s a problem: it was so tightly coupled to Tauri that the work couldn’t be enjoyed by other projects (not even the ones like Dioxus who were using Tauri’s underlying technology of Tao + Wry).