/
Navigation
Chronicles
Browse all articles
Explore
Semantic exploration
Research
Entity momentum
Nexus
Correlations & relationships
Story Arc
Topic evolution
Drift Map
Semantic trajectory animation
Posts
Analysis & commentary
Pulse API
Tech news intelligence API
Browse
Entities
Companies, people, products, technologies
Domains
Browse by publication source
Handles
Browse by social media handle
Detection
Concept Search
Semantic similarity search
High Impact Stories
Top coverage by position
Sentiment Analysis
Positive/negative coverage
Anomaly Detection
Unusual coverage patterns
Analysis
Rivalry Report
Compare two entities head-to-head
Semantic Pivots
Narrative discontinuities
Crisis Response
Event recovery patterns
Connected
Search: /
Command: ⌘K
Embeddings: large
TEXXR ▲
TEXXR

Chronicles

The story behind the story

← → days · ↑ ↓ browse · Enter similar · o open

Microsoft announces “Super Duper Secure Mode” for its Edge desktop browser, which disables V8's JIT, allowing for security features like Arbitrary Code Guard

Microsoft said today it plans to run an experiment in its Edge web browser where it will intentionally disable …

The Record Catalin Cimpanu

Context & Ripple Effects

Edge was built with a security posture that excluded legacy browser components, including ActiveX, VB Script and browser helper objects. Microsoft later moved Edge to Chromium while committing to invest in that engine, so the new experiment tests how far its hardening can go within the Chromium-based browser.

The experiment extends Edge’s safety-oriented product work beyond a Kids Mode with strict tracking prevention: rather than changing defaults for a user segment, it alters a core code-execution path to make protections such as Arbitrary Code Guard available.

First-order effects

  • Microsoft can test a desktop Edge configuration that disables V8’s just-in-time compiler and supports Arbitrary Code Guard, prioritizing exploit resistance in that mode.
  • Edge desktop users participating in the experiment face a more restrictive browser execution model than the standard JIT-enabled configuration.

Second-order effects

  • Microsoft’s Edge team must assess whether the security benefit justifies the compatibility and performance trade-offs inherent in removing JIT compilation before broadening the mode.
  • The move puts browser hardening emphasis on execution architecture rather than only privacy and content controls, extending the direction set by Edge’s earlier removal of legacy extensibility components.

Third-order effects

  • If JIT-free modes prove usable, browser security may increasingly segment into selectable execution profiles that trade some performance for stronger platform-enforced protections.
  • The longer-term competitive distinction for Chromium-based browsers may depend less on the shared rendering engine and more on vendors’ willingness to maintain differentiated security configurations.

The trend: Browsers are moving from removing legacy attack surfaces toward optional, deeper execution-layer defenses within shared browser engines.

Related: Edge · Microsoft · Edge drops legacy browser components for security · Microsoft commits to Chromium-based Edge · Edge Kids Mode adds strict safety defaults

Related Coverage

Discussion

  • @chvest Chris Vest on x
    “We see that most tests see no changes with [JavaScript] JIT disabled. There are a few improvements and regressions, but most tests remain unchanged. Anecdotally, we find that users with JIT disabled rarely notice a difference in their daily browsing.” https://microsoftedge.githu…
  • @jcolman Jonathon Colman on x
    “There are only two hard things in Computer Science: cache invalidation and naming things.” https://therecord.media/...
  • @jermolene Jeremy Ruston on x
    So, Microsoft finds that “JITs” and other leading edge browser optimisations are responsible for most JavaScript bugs (and hence exploits), and even better that turning off those optimisations is imperceptible almost all of the time. Meanwhile Google blames devs for using alert()…
  • @never_released Longhorn on x
    Oh wow, https://microsoftedge.github.io/ .... JITless Microsoft Edge, if this works with proper performance for everyone at the end, will be utterly amazing. (And hello iOS too)
  • @rich_harris Rich Harris on x
    incredible — disabling JITs might have *positive* impact on perceived performance, and makes browsers more eco-friendly, all while protecting users from exploits. will follow this research with interest https://microsoftedge.github.io/ ... (h/t @dmitriid)
  • @gcaughey Ginny Caughey on x
    Interesting details about Edge experimental Super Duper Secure Mode: https://microsoftedge.github.io/ ... I can't notice any performance difference with my company website, but be aware Web Assembly isn't supported yet in this mode.