4 ms·
How is this different / better than Leptos or Dioxus? https://leptos.dev/ https://leptos.dev/ https://dioxuslabs.com/ https://dioxuslabs.com/
by josephg 3mo ago
How is this different / better than Leptos or Dioxus?
https://leptos.dev/ https://leptos.dev/
https://dioxuslabs.com/ https://dioxuslabs.com/
- tekacs 3mo agoI have the same question, but it doesn't look like this is actually Rust code; it's just a compiler for their custom... syntax (?) written in Rust. https://buildnectar.com/docs/language-reference https://buildnectar.com/docs/language-reference This random custom language, I guess.
- blakeburnette 3mo agoLargely the difference, as I am aware of those two options. They build on the traditional DOM. I took this approach, and as I was attempting to speed processes up I was consistently running into issues where I was beholden to C++ and Blink. The more I tried to beat Svelte, it seemed that I was hitting limitations with traditional web architectures, javascript and the DOM itself. They are fantastic options. I support writing Rust everywhere. But I was kind of over the many issues with JS (security, performance limitations, etc...). I had a vague curiosity about the ability to abandon the traditional DOM, thoughts on WASM and long story short I went for it. So what you are seeing is not a traditional DOM, inspect the demo page and compare it to the Svelte demo. I built my own DOM, but when you compile Nectar it automatically gets picked up as a traditional DOM by screen readers and SEO (this still needs some love). Initial loads, I am still really struggling with, but sorts and filters are quite performant.