Trust was my biggest objection to it... There was no reasonable/complete Linux implementation available, and at that point Microsoft had never supported a technology (other than office) outside of Windows for more than 2 releases that I could recall.
In general, I really liked the package model, it's close to what I'd hoped Flash would become after Adobe acquisition. I do like React a bit better than Silverlight, but the tech and usability wasn't really bad, just more of a risk aversion for myself.
If MS had created an open-source client implementation that was patent unencumbered that other browsers could have integrated, with open tooling, I think it would have gone better. Can't speak to this implementation. For the Blazor efforts, payload size just feels excessively huge to me, and server-side renders feel as laggy as the original ASP.Net lifecycle round trip.
I'd probably be more inclined to work towards tooling for other languages that have a lighter wasm target (Rust in particular) and either web canvas or something like yew. All of that said, I'm pretty happy with React these days.
In general, I really liked the package model, it's close to what I'd hoped Flash would become after Adobe acquisition. I do like React a bit better than Silverlight, but the tech and usability wasn't really bad, just more of a risk aversion for myself.
If MS had created an open-source client implementation that was patent unencumbered that other browsers could have integrated, with open tooling, I think it would have gone better. Can't speak to this implementation. For the Blazor efforts, payload size just feels excessively huge to me, and server-side renders feel as laggy as the original ASP.Net lifecycle round trip.
I'd probably be more inclined to work towards tooling for other languages that have a lighter wasm target (Rust in particular) and either web canvas or something like yew. All of that said, I'm pretty happy with React these days.