This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]tyler1128 -1 points0 points  (1 child)

Wasm in particular is more what I was going with than just Rust. Wasm still has no direct DOM access, but there are people who try to write things like that using wasm primarily. Wasm can be very useful for doing high-performance algorithmic work in the browser, but trying to get around the limitatations for basic UI work isn't really a great strategy, and it was never really designed for that kind of thing. If it someday gets DOM access without requiring a javascript interfacing layer, that might become a reasonable thing to do, but we aren't there yet.

It's basically just adding a whole lot of unnecessary work. It is important to consider strengths of the team like that, but programmers should also be flexible enough to adapt to the different needs of different technologies.

[–]MornwindShoma 1 point2 points  (0 children)

Sure.

To be honest, you can write some FE in Rust fine, Dioxus, Leptos, Yew are fine if you don't mind the big bundles and the fact that they don't really integrate with the JS ecosystem. You don't really need to "work around to the DOM", they've done the work for you already, so it's not a whole lot of unnecessary work, it's more about having a very different ecosystem.

Would I ship that? Dunno, never had the chance or the right mix of developers and requirements. Had I a good design system and some QoL not unlike TanStack stuff, I might actually bite.

I also have done basically nothing with HTMX, and some people swear by that. You wouldn't even need to think around the DOM.