Microsoft Edge Experimenting with a Super Duper Secure Mode
microsoftedge.github.io
Microsoft Edge Experimenting with a Super Duper Secure Mode
1–10 of 67 posts
Re: Microsoft Edge Experimenting with a Super Duper Secure Mode
#2This is actually really interesting. Bravo to the Edge team.
And if I remember correctly, writeable memory pages were the main reason why iOS banned browsers like firefox from embedding their own rendering engines.
Perhaps this kind of approach could address such concerns and enable other rendering engines.
Re: Microsoft Edge Experimenting with a Super Duper Secure Mode
#3I'm surprised at how little regressions there were in the tests they run, given they completely disabled JIT. This could be very useful as a default 'mode' for websites, with JIT able to be turned on for trusted websites if the user would like more performance.
Re: Microsoft Edge Experimenting with a Super Duper Secure Mode
#4Interesting but I am not a fan of how they don’t mention disabling features like WebAssembly in the short description.
Re: Microsoft Edge Experimenting with a Super Duper Secure Mode
#5This is actually really interesting. Bravo to the Edge team. And if I remember correctly, writeable memory pages were the main reason why iOS banned browsers like firefox from embedding their own rendering engines. Perhaps this kind of approach could address such concerns and enable other rendering engines.
Well, like the real reason is that the web is a threat to the app store. So, likely we'd just see some new excuse (if they even bother)
Re: Microsoft Edge Experimenting with a Super Duper Secure Mode
#6Interesting but I am not a fan of how they don’t mention disabling features like WebAssembly in the short description.
they did mention it in the long description. It's off for now but they are planning on turning it on.
I'd guess it's safer than JIT because the translation to assembly is simple, or can be simple. It's not trying to do the complicated process of analyzing a dynamically typed language and applying different ways of optimizing.
Re: Microsoft Edge Experimenting with a Super Duper Secure Mode
#7This is actually really interesting. Bravo to the Edge team. And if I remember correctly, writeable memory pages were the main reason why iOS banned browsers like firefox from embedding their own rendering engines. Perhaps this kind of approach could address such concerns and enable other rendering engines.
Well, like the real reason is that the web is a threat to the app store. So, likely we'd just see some new excuse (if they even bother)
Ironically, in the early days Apple was redirecting developers to the web to build apps for the iPhone. But then it seems they discovered a money minting model.
Re: Microsoft Edge Experimenting with a Super Duper Secure Mode
#8I'm surprised at how little regressions there were in the tests they run, given they completely disabled JIT. This could be very useful as a default 'mode' for websites, with JIT able to be turned on for trusted websites if the user would like more performance.
They did note that the JavaScript benchmarks were reduced by upto 58%, while noting that users won't generally notice the difference.
I would be interested to see how this affects the performance of websites that make use of complex JavaScript for things like charting/visualization (like the D3.js demos, or online formulae graphing tools), audio waveform rendering/processing, games, and other complex uses of JavaScript (including things like vue, react, bootstrap or other JavaScript UI frameworks).
Re: Microsoft Edge Experimenting with a Super Duper Secure Mode
#9I'm surprised at how little regressions there were in the tests they run, given they completely disabled JIT. This could be very useful as a default 'mode' for websites, with JIT able to be turned on for trusted websites if the user would like more performance.
I know where you're going but this can easily turn upcoming players into second class, further reinforcing big tech monopoly.
Re: Microsoft Edge Experimenting with a Super Duper Secure Mode
#10I'm surprised at how little regressions there were in the tests they run, given they completely disabled JIT. This could be very useful as a default 'mode' for websites, with JIT able to be turned on for trusted websites if the user would like more performance.
I know where you're going but this can easily turn upcoming players into second class, further reinforcing big tech monopoly.
Assuming "trusted websites" is a user preference, why should it matter?