Comment by drnick1
1 day ago
I am happy this one died. It was just another attempt by Microsoft to sidestep open web standards in favor of a proprietary platform. The other notorious example is Flash, and both should be considered malware.
1 day ago
I am happy this one died. It was just another attempt by Microsoft to sidestep open web standards in favor of a proprietary platform. The other notorious example is Flash, and both should be considered malware.
Open web standards are great but consider where we could have been if competition drove them a different way? We're still stuck with JavaScript today (wasm still needs it). Layout/styling is caught up now but where would we be if that came sooner?
> Open web standards are great but consider where we could have been if competition drove them a different way? We're still stuck with JavaScript today (wasm still needs it). Layout/styling is caught up now but where would we be if that came sooner?
Why do you think JavaScript is a problem? And a big enough problem to risk destroying open web standards.
It's not that it's a problem I just don't think it's the best place to be. It was not designed to be used like this. Yes, it's better now but it's still not great - you still ship JS as text blobs that need to be parsed and compiled by every browser.
I don't see how alternatives to JavaScript are a risk to open web standards. WebAssembly is itself a part of those same standards. It's just a shame that it was built as an extension of JavaScript instead of being an actual alternative.
The same reason Typescript exists
3 replies →
Flash & Silverlight were both ahead of the current open web standards at the time. They also didn't suffer as much from the browser wars.
Flash's ActionScript helped influence changes to modern JS that we all enjoy.
You sometimes need alternative ideas to promote & improve ideas for open web standards.
What web standards? :-)
Stuff like angularjs was basically created for the same reason flash/silverlight went down — iphone
Did Silverlight have the same security issues as Flash?
Yes, even using C# couldn't save them.
> A remote code execution vulnerability exists when Microsoft Silverlight decodes strings using a malicious decoder that can return negative offsets that cause Silverlight to replace unsafe object headers with contents provided by an attacker. In a web-browsing scenario, an attacker who successfully exploited this vulnerability could obtain the same permissions as the currently logged-on user. If a user is logged on with administrative user rights, an attacker could take complete control of the affected system. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights. Users whose accounts are configured to have fewer user rights on the system could be less impacted than users who operate with administrative user rights.
https://learn.microsoft.com/en-us/security-updates/securityb...
Probably didn’t have the level of adoption needed for the nefarious types to justify spending time finding Silverlight exploits.