Post

This is good for everyone that Java is targeting #Wasm, but I have to admit I always feel a bit frustrated when an article like this lists wasm-friendly languages and omits #csharp. As far as I know, #blazor is the only wasm UI framework, and I've been writing production apps with it for 4 years.

Matt Butcher@technosophos.bsky.social

Good article on the news about Java-to-Wasm compilation. thenewstack.io/graalvm-fina...

thenewstack.ioGraalVM (Finally) Gets Java for WebAssemblyUp until now, Java has been neglected, as WebAssembly modules have been more conducive with C and C++, Rust and Go, and now even Python is embedded as an interpreter.

24/4/25, 12:11 pm6 reposts9 likes

Matt Butcher

@technosophos.bsky.social

24 Apr 2025

I agree. The entire .NET ecosystem is actually on the avant-garde of WebAssembly. In addition to the Blazor work, the .NET team has done some awesome stuff. Here, for example, is how we used Aspire. www.fermyon.com/blog/observi...

fermyon.comObserving Spin Apps with OpenTelemetry and the .NET Aspire DashboardLearn how to observe your Spin apps using the otel plugin for Spin and the .NET Aspire Dashboard.

#1 text-overflow: ellipsis; hater

@nekotachi.bsky.social

25 Apr 2025

rust has quite a few GUIs that run on wasm, as well as stuff like Yew

Tim Purdum

@timpurdum.dev

25 Apr 2025

Thanks! I had trouble finding info on these, finally found yew by name. Maybe the issue with these articles is not only language bias but usage bias. Everyone seems to talk about replacing containers with something faster and smaller, but the UI applications are important too.