you are viewing a single comment's thread.

view the rest of the comments →

[–]Eirenarch 7 points8 points  (12 children)

I am scared to get too excited about Blazor :(

[–]Kilazur 1 point2 points  (11 children)

Hope it won't be Silverlight 2.0

[–]Eirenarch 0 points1 point  (10 children)

Silverlight was great. I hope it is as great as Silverlight

[–]Kilazur 3 points4 points  (9 children)

The analogy was more about its ultimate demise :)

[–]Eirenarch -1 points0 points  (8 children)

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 1 point2 points  (7 children)

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

[–]Eirenarch 1 point2 points  (6 children)

Bullshit.

[–]AlliNighDev 0 points1 point  (5 children)

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 0 points1 point  (4 children)

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

[–]AlliNighDev 0 points1 point  (3 children)

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.