Show HN: Sauron – A web framework in Rust that adheres to the Elm architecture

Between this and Blazor ( <a href="http:&#x2F;&#x2F;blazor.net&#x2F;" rel="nofollow">http:&#x2F;&#x2F;blazor.net&#x2F;</a>, among other wasm projects I&#x27;m forgetting right now), I&#x27;m glad more complicated UIs are being once again designed on the backend and keeping bundle sizes (relatively) small, rather than making <i>everything</i> in JS on the frontend and expecting everyone to download megabytes of code to visit a website.<p><i>I&#x27;m looking in your direction Medium, at 6MB with a cold cache!</i>

From the README<p><pre><code> One crate to rule the DOM One crate to find the elements One crate to bring JSON And in the Rust code bind Strings</code></pre>

Sauron looks really great and I for one am super excited about the future of Rust + WASM for web apps(with Backend). However I am a bit concerned that even the minimal example is 1.17MB of WASM which seems really high since Rust compiled to WASM should be quite small.

Elm gets plundered repeatedly before it ever reaches version 1.0. Is name-brand Elm still growing in adoption?

How is Elm&#x2F;Om doing so well in those benchmarks? I would think that most wasm frameworks would be able to blow past any js framework fairly easily.<p>edit: Ah, calls to js are still necessary to create DOM elements, so there&#x27;s lots of back and forth necessary in the wasm frameworks.

Obvious questions first: How does it compare to Yew?

Performance: Is not too bad.<p>I laughed at this, idk why.

Would there be an easy&#x2F;straightforward way to put a jsx transpiler in front of the rust compilation step, potentially with hot reloading?<p>I realize that jsx in react is really just calls react.createElement, but I do think it&#x27;s a very useful abstraction when you&#x27;re ultimately constructing html.

(Disclaimer: very limited knowledge about WASM)<p>Curious as to how WASM impacts browser caching?<p>In the JS scenario, several modules will be cached and change in one may still allow usage of other cached modules, thereby reducing future load times.<p>How will that work in WASM work, since I&#x27;m assuming that the entire app will be packaged at build time as a single binary. Is the assumption even correct?<p>Or, is it simply a question of architecting your app well into several WASM modules, since I&#x27;m assuming WASM modules (or whatever they are called) can call each other and do lazy loading.

Commend on the attempt, foward thinking now wasm is getting more traction. but I can imagine that view syntax turning into an insane &gt; circa the old days of callbacks in nodejs

Looks cool, really like the name. It’s always interesting to me to see other developers who are good at branding, despite no obvious marketing background.

Hey, interesting! Have you seen dodrio from mozilla? Could be a good candidate for your diffing algorithm and improve performance a lot.

Check out <a href="http:&#x2F;&#x2F;blazor.net&#x2F;" rel="nofollow">http:&#x2F;&#x2F;blazor.net&#x2F;</a>

So one thing, these are still slower and more expensive in performance, compared to JS frameworks, right?

Slightly off topic - I can’t imagine calling the framework Sauron and posting a photo from the LOTR movie is legal.

I&#x27;m still waiting for something like scala.js for Rust. I don&#x27;t like the thought of using two different programming languages and currently it seems scala.js is the most dependable front-end library

Folks please take care in how you name your open source project. Sauron is not something I want to think about every time I sit down to work, neither are cockroaches (CockroachDB).