[JustLurking2022]

Getting these kinds of applications out of Silverlight or desktop apps was one of the greatest steps forward I've seen in at least a couple large enterprise shops - and Blazor definitely feels like a step back in that regard.

Honestly, it's one of the issues I see with WASM as a whole. The JavaScript ecosystem is almost implicitly supportive of open source, since that's essentially what gets delivered to the browser. WASM feels like it take us back towards walled gardens where you have to buy Telerik or Dundas libraries to get the widget you want to use, and then find out they don't play nicely with some other part of your stack. For all but the must graphically intensive use cases, or companies that can afford to own their stack from the ground up, I see little reason to adopt it.

[tonyedgecombe]

>Getting these kinds of applications out of Silverlight or desktop apps was one of the greatest steps forward I've seen in at least a couple large enterprise shops - and Blazor definitely feels like a step back in that regard.

The thing my enterprise customers wanted to avoid was deploying software on their desktops. They didn't even like rolling out Office. Presumably Blazor eliminates that problem because the whole thing is delivered over http.

[kaba0]

> The JavaScript ecosystem is almost implicitly supportive of open source

JS is basically a compilation target nowadays. Don’t tell me that a minified, tree-shaken JS file somehow helps open-source. Sure, .NET is definitely not the panacea of open-source, but that is not inherent in the technology, but the politics around.

[electroly]

The person you're replying to is talking about Blazor Server which does not involve WASM at all.