Emerging Rust GUI libraries in a WASM world

Post by davidatbu » Sat, Apr 29, 2023, 5:10 AM UTC

ljsb wrote: post #210

davidatbu wrote: post #197

Earlier quoted context omitted.

While I'm usually a no-macros kinda guy, but (I believe) leptos and dioxus provide tooling to hot-reload markup-only changes without (incremental) recompilation. Do you think that would be possible withour macros?

I can't think of any practical way to do that without macros, unfortunately. I've found incremental compilation to be pretty speedy for small markup changes so far though. I do tend to put the presentation code in it's own crate for larger projects, which might make a difference. Maybe as my projects get bigger I'll start to run into problems. Some other ideas: - Temporarily stopping the rust-analyser server to avoid…

Thanks for the ideas! Separating out presentation crate into it's own crate sounds like a great idea. Re "temporarily stopping rust-analyzer", I came across this trick[0] to make RA use a different build path (trading off disk-space for speed, but I mean, disk space is cheap).

Re: cranelift, I gotta check that out! Thanks for the reminder!

[0] https://github.com/rust-lang/rust-analyzer/issues/6007#issue...

Post by pkolaczk » Sat, Apr 29, 2023, 7:38 AM UTC

steveklabnik wrote: post #255

pkolaczk wrote: post #212

Earlier quoted context omitted.

How come Rust appears at the top of most loved languages in the SO survey so many years in a row? And doesn't even make into the "most dreaded" list at all (when many simpler languages do make into that list)? Also, there aren't any other mainstream languages with borrow checker at the moment. The problem with Rust is that it introduces many novel ideas, not just some old ideas wrapped in a different syntax (e.g. lik…

> How come Rust appears at the top of most loved languages in the SO survey so many years in a row? And doesn't even make into the "most dreaded" list at all Because these two lists are mutually exclusive. On the survey they ask: * Do you use X today? * Do you want to continue to use X in the future? "Most loved" means "the ratio of yes/yes answers is high", and "most dreaded" means "the ratio of yes/no answers is hi…

If so few people say yes/no then this means to me that either the difficulty is not really as bad as some people try to paint it here (under assumption people don't want to continue using a language that is frustrating), or that indeed the difficulty level might be high but developers get a lot in return, so it is still worth to pay that price and continue using Rust, which means - maybe it is difficult, but it is still productive.

It is very hard if even possible to objectively assess the difficulty of the language, because difficulty is inherently subjective and depends heavily on prior experience. The fact that there are many people who claim to be more productive in Rust than e.g Python or Java, but at the same time many others that don't share that opinion, IMHO supports my claim this is mostly a matter of a paradigm shift.

Also I noticed many developers somehow don't count the difficulty to fix bugs towards the difficulty of the language. And maybe that's also an explanation why we end up with so vastly different opinions.

Re: Emerging Rust GUI libraries in a WASM world

Re: Emerging Rust GUI libraries in a WASM world