Code-signing and certificates are still necessary even in a WASM environment. Once all your software moves into the web browser, all your important data lives t

Code-signing and certificates are still necessary even in a WASM environment. Once all your software moves into the web browser, all your important data lives there too and the risk profile of all the third-party code loaded into your websites is incredibly high, just like it is for Chrome and Firefox extensions. Right now if you're a Windows dev you get harassed by SmartScreen, but if you're a web dev you get to either reinvent the entire stack from the ground up (to control it) or pull in 20 different third-party dependencies, none of which are code-signed, without any easy methods to ensure integrity other than manually listing specific hashes in a fashion that causes your website to break any time a vendor pushes new code. Don't get me started on software that currently only works if deployed as an extension - being an extension developer is one of the worst development experiences on earth