Thread by @spoofyroot

Happy to share a little experiment we are trying. microsoftedge.github.io/edgevr/posts/S… I am not sure if it will stick but we will see. Here is how I personally think about the matter 1/?

The impact of security bugs today is far different than it was 10 years ago. Entities like NSO Group and their customers have leveraged these bugs to do some horrible things to journalists, human rights activists, and others. 2/?

So it is worth reconsidering previously held ideas about the compromises made when building software. The JIT is a great example of a performance improvement that is nice but not required for most of the web to work. It also introduces a lot of attack surface 3/?

and forces us to disable some security protections. So we should ask is it worth it? I personally prefer security improvements over the performance gains. Although I am not sure the broader market shares that view. Either way I think giving users more choice is a good idea. 4/?

My hope is that we can find a better way to balance the trade-offs. In our early testing we find that users often don't notice the difference. I would encourage people to try the feature in Edge Beta to see for yourself. edge://flags/#edge-enable-super-duper-secure-mode 5/?

At the moment we are disabling JIT and enabling CET in the renderer process. ACG enablement is next after we do some testing. We also have plans for Android and Mac as well. Android being the most interesting since mobile is such a key target 6/?

I'm not sure if this will land as a feature. But I think this experiment is worth a shot. If you try it please share your feedback in Edge (click the 3 dots -> feedback) or post on the forum techcommunity.microsoft.com/t5/microsoft-e… . We are curious to see if this is something users want. 7/?

Also .. taking suggestions for the feature name as well :) Although we enjoy saying "Super Duper" in meetings at some point that needs to change. 8/8

One more thing I didn't mention here (but discussed in the blog) WASM does not work in this mode currently. It is something we're working on addressing.