TE
TechEcho
Home24h TopNewestBestAskShowJobs
GitHubTwitter
Home

TechEcho

A tech news platform built with Next.js, providing global tech news and discussions.

GitHubTwitter

Home

HomeNewestBestAskShowJobs

Resources

HackerNews APIOriginal HackerNewsNext.js

© 2025 TechEcho. All rights reserved.

Modernizing the DOM Tree in Microsoft Edge (2017)

26 pointsby jasimalmost 4 years ago

3 comments

makepanicalmost 4 years ago
This is an article from 2017 and seems to primarily target the &quot;old&quot; Edge.<p>Later Microsoft moved to using Edge based on Chromium.<p>(Previous discussion <a href="https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=14149647" rel="nofollow">https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=14149647</a> )
dmitriidalmost 4 years ago
(2017)<p>And then Microsoft gave up on developing their own browser engine and switched to Chromium.<p>And then there were only two competitors to Google&#x27;s increasing subsuming of the Web.
评论 #27576973 未加载
评论 #27576951 未加载
imvetrialmost 4 years ago
Before reading -<p>Wait, how they are going to modernise something that is working well?<p>What do they mean by modernise?<p>Is the modernise technique really better ?<p>First read - There is really no modernisation done and no improvements at all until I saw the chart.<p>Second read - Very carefully trying to understand and found that they removed legacy technique to access a node and replaced it with a node with four pointers - parent, first-child, next, and previous sibling.<p>Its a neat work because trying to migrate a older technique to newer ones will require deeper knowledge !