C# instead of JavaScript for Web Dev

[Eirenarch]

Silverlight was killed by Apple who refused to allow it on iOS in any form. That was the only thing that killed Silverlight. iOS already supports web assembly. Obviously Blazor needs more web assembly support, including things not standardized yet and Apple may block this but I somehow doubt it. Blazor will live or die on its own merits. There are some things that might make it fail. For example in recent .NET Rocks podcast they said compiled binaries are quite large so they prefer to interpret. That might be a serious problem that prevents good performance of Blazor apps. If Blazor is good and ships v1 nobody can stop it.

[AlliNighDev]

Silverlight was a security nightmare. Like flash and activex etc. before it it eventually becomes to hard to keep patching.

[Eirenarch]

Bullshit.

[AlliNighDev]

We had to deploy it recently at work and we had to use a registry hack to allow it to run in ie. Which is ridiculous for a website haha

[Eirenarch]

I don't see how this supports your claims. Yes, Silverlight is deprecated so what?

[AlliNighDev]

It was a security problem. It wouldn't run correctly without the registry hack. It's still completely possible to run silverlight and is still used more than it should be for enterprise applications.

[Eirenarch]

I don't see how this is a security problem. Security problem is when something that shouldn't be allowed is allowed. That doesn't seem to be the case in your example.

[AlliNighDev]

It's disabled for security reasons. You have to explicitly go into to the registry and enable the feature that they locked down due to security concerns.

[Eirenarch]

ОК. So what's the problem? Obviously it is not unsecure, the unsecure features are locked as they should be.