re: How Blazor Is Going to Change Web Development VIEW POST


So basically, from what I understand, it does the same thing ActiveX and Java Applets did back in the day?

And don't we already have Unity and various other WASM frameworks for browser games?

Basically the way I see it, this is the same thing .Net does with everything. Instead of devs learning a language they incorporate it poorly into the framework (see React.NET).

Not to be the one carrying the pitchfork but I don't really see a (near) future where we start packaging JS as binary.

There's also a host of other issues ranging from browser compatibility to security settings that disable wasm features and things like chink splitting which JS already does well enough. Though that last one I presume should exist as a loader mechanics.

code of conduct - report abuse