blazor

I don't think "was always" is an accurate statement However, above and beyond free, it is also a collection of ECMA standards https://learn.microsoft.com/en-us/dotnet/fundamentals/standa... Now, don't get me wrong: I have grave suspicions there is currently only one actual implementation of them (I don't count hobby, or abandonware, ones) but IMHO "actual standard" combined with "for real reference implementation" is way better than just reference implementation --- since I'm still within the edit window, the MAUI referenced by the sibling comment is MIT licensed https://github.com/dotnet/maui https://github.com/dotnet/blazor (Apache 2) is marked an archived, and points to https://github.com/dotnet/aspnetcore (MIT) but command-f blazor on its readme is nothing so :shrug:

There are already several libraries that allow you to write React-like SPAs in the browser via WASM. The two largest are Yew (Rust), Vugu (Vue-esque but with Go instead of JS), and Blazor (C#) https://github.com/yewstack/yew https://github.com/vugu/vugu https://github.com/aspnet/Blazor All are perfectly viable for production apps as of today and not much more difficult than writing React, given you have some familiarity with their implementation language.

Honestly looking forward for WebAssembly to mature, just seeing what Microsoft has done with Blazor[0] is impressive, and that's just scratching the surface. https://github.com/aspnet/Blazor

Early Blazor prototypes used a compact .NET runtime (including assembly execution, garbage collection, threading) that compiled to a mere 60KB of WebAssembly. They moved to mono, so that isn't true now. https://github.com/aspnet/Blazor/wiki/FAQ

>Serious question: Why would you use WASM for a dynamically typed, GC'ed language? The point is using it as universal bytecode for deploying anything you want. Ideally we could do front end web development with any language/framework combo and just compile to WASM. It seems like that's the future, with things like Blazor getting major support, and that JS will probably mostly die out over the next 5 years. https://github.com/aspnet/Blazor

And now with Microsoft's Blazor[0] technology you're more likely than ever to see C# on client-side web applications through WebAssembly. [0]: https://github.com/aspnet/Blazor

WebAssembly (currently) doesn't have direct access to DOM, so it has to use JS, hence the GC. Here is some of the JS for Blazor: https://github.com/aspnet/Blazor/tree/master/src/Microsoft.A...

Tree-shaking is already there: https://github.com/aspnet/Blazor/issues/1076

Blazor is coming. It's not GA yet. https://github.com/aspnet/Blazor

"Two major forces outside of Microsoft's control curtailed .NET's planned world dominance: (1) the rise of Javascript in the browser which negated .NET Silverlight, and also Java applets and Flash. (2) the rise of Apple iOS and Android." I agree with those 2 forces: 1) the raise of javascript: Now is starting to develop an answer to this in Blazor (https://github.com/aspnet/Blazor) 2) iOS and Android: both are here to stay, so Xamarin is the answer. I have been using Xamarin for iOS and all though still lack of some maturity, in its actual form is very viable.

.NET Core is superior than Mono for Server Software like ASP.NET Web Apps but Mono is more suitable for embedded environments like iOS/Android/PlayStation/Xbox,etc and is also what's used in Microsoft's new Blazor project for running C# Apps in Web Assembly (https://github.com/aspnet/Blazor).

Depends if you define WebAssembly as "JavaScript" or not. Have the days of hand-writing raw JS peaked? More than likely. Between TypeScript and other transcompilers, and the impending threat of WebAssembly being able to consume other languages and output browser executable code. A project like Microsoft's Blazor[0] might ultimately fail, but that type of compiled from language to WebAssembly likely is the future. But if you define WebAssembly as "JavaScript" then I guess we haven't hit peak JS. [0] https://github.com/aspnet/Blazor