elm-ui VS Seed

It's been a few years, but last time I built a non-trivial Elm app, I used elm-ui. Otherwise, I've used either vanilla CSS with the Meyer reset (am I dating myself?) or SCSS.

"clean" means you are used to it. ELM is a totally new language (not like JS and TS) based on a paradigm (functional programming) that you are probably not used to. And it is based on the ML type system (different from what you are used to). So it is a lot of new things at once. "Reinventing the wheel" is an unfortunate side-effect of using a different way to do things. Some things can be copied verbatim, some are totally different. Check out "elm-ui" (https://package.elm-lang.org/packages/mdgriffith/elm-ui/latest/) for a very different and refreshing view in UI code in ELM (that will appeal to the mostly-backend developers in your workplace).

I use Elm for my project. Once you accept thinking the way it wants you to, it's a delight to develop front-end with it.

Side advantage, Elm-UI frees you from CSS: https://package.elm-lang.org/packages/mdgriffith/elm-ui/late... it's like Tailwind but deeply intertwined with the language.

https://elm-lang.org

The last advice I could give is to try elm-ui (https://github.com/mdgriffith/elm-ui) for your user interface. It's amazing how great that is compared to traditional ways of building a frontend layout.

The library elm-ui makes it easy to create a nice user interface. I am unaware of anything similar for Rust+WASM, so I would have been forced to deal with HTML and CSS.

There are several things named elm-ui. It's the author of a different library than what is usually understood when someone refers to elm-ui (which is https://package.elm-lang.org/packages/mdgriffith/elm-ui/late...)

Foregoing CSS all together by using a different approach to UI construction (elm-ui)

Right now I'm just using the built in from the UI library I used for the sake of ease as I didn't find a perfect solution and it seemed good enough for now: Github Link to source, which it looks like would classify your laptop as a tablet, whoops!

Practically every Rust web frontend I've seen takes a react-like approach, with "hooks" to store all of the state in. The now-abandoned Seed and Yew's struct components use a message-passing approach, where the state is stored as member variables on the struct representing the component that are updated based on messages dispatched by event handlers. There's also egui, which has a completely different paradigm that involves making the UI from scratch every frame based on the app's current state. It's not a web framework the same way as the others, but it can draw its UI to a web canvas just fine.

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

An authentication system is an integral part of modern applications. It's so important that almost all modern applications have some sort of it. Because of their critical nature, such systems should be secure and should follow OWAP®'s recommendations on web security and password hashing as well as storage to prevent attacks such as Preimage and Dictionary attacks (common to SHA algorithms). To demonstrate some of the recommendations, we'll be building a robust session-based authentication system in Rust and a complementary frontend application. For this article series, we'll be using Rust's actix-web and some awesome crates for the backend service. SvelteKit will be used for the frontend. It should be noted however that what we'll be building is largely framework agnostic. As a result, you can decide to opt for axum, rocket, warp or any other rust's web framework for the backend and react, vue or any other javascript framework for the frontend. You can even use rust's yew, seed or some templating engines such as MiniJinja or tera at the frontend. It's entirely up to you. Our focus will be more on the concepts.

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.

Aside from Blazor there's already some other projects like Yew (rust), seed (rust), asm-dom (C++) and vugu (Go) and more that have decent followings and activity. A lot more (especially managed languages) are waiting for some features to come online like wasm GC and host bindings (direct wasm access to browser apis which includes the DOM). It'll take a bit of time, but it'll get there eventually.

To click * https://crates.io/crates/percy * https://crates.io/crates/seed * https://crates.io/crates/perseus * https://crates.io/crates/sycamore

For desktop apps maybe check out Tauri . You can use it with a lot of (web)frontend options including yew/wasm (also Seed ) if you want to go 100% Rust. Actix and Rocket are options for web framework. Also have look at the Building a Command Line Program in the book. I found it really helpful since i am just starting to learn myself.

I haven't been keeping up with it, but have heard of it. If ibrecall correctly it was created by the developer that initially developed seed (https://seed-rs.org/)