Forums
New posts
Search forums
News
Security News
Technology News
Giveaways
Giveaways, Promotions and Contests
Discounts & Deals
Reviews
Users Reviews
Video Reviews
Support
Windows Malware Removal Help & Support
Inactive Support Threads
Mac Malware Removal Help & Support
Mobile Malware Removal Help & Support
Blog
Log in
Register
What's new
Search
Search titles only
By:
Search titles only
By:
Reply to thread
Menu
Install the app
Install
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Forums
Software
Browsers
Microsoft Edge
Microsoft Edge Stable (Chromium) Now Available for Download
Message
<blockquote data-quote="Lenny_Fox" data-source="post: 858661" data-attributes="member: 82776"><p>Indecisive: V80 contained many high-risk fixes, so was a major update.</p><p></p><p>Imagine a browser being an user interface with a 'master controller' launching other parts of which the renderer is the most important module. The renderer in its turn processes HTML (the content), CSS (the layout in which content is displayed) and runs the V8 javascript engine (processing the javascript which adds functionality).</p><p></p><p><strong>On the upside (in favor of Edge-chrmium/Microsoft)</strong></p><p>In terms of maintenance Opera seems to have the smartest architecture*, so Opera should be able to follow Chrome faster than other chromium based browsers like Brave or Edge-chromium. Microsoft seemed to beat both (Opera and Brave) in terms of adopting this major V80 release</p><p></p><p>*) When comparing Chrome with Opera, you will notice that all the site-permissions are identical and that Opera has an occasional extra flags which they clearly mark as Opera specific, e.g. one general settings for DNS over HTTPS and a Opera-DOH. Opera has neatly limited itself to changes in the GUI and providing bolt-on VPN functionality or modular extra ad-blocker functionality. The build-in ad-blocker seems to use the rule engine of an existing extension, but has its own API and in memory data structure (where rules are stored), which seems to be a simpler version of the current Chrome API (play with advanced ABP-rules and you will notice some things, usually advanced features don't work).</p><p></p><p><strong>On the downside (against Edge-chromium/Microsoft)</strong></p><p>When you clone a browser you normally would not touch the renderer and the master controller. When you compare the site-permissions of Edge-chromium with Chrome, you will notice some differences. The same applies for the flags. This indicated that Microsoft did not restrict the changes to the just the GUI or bold-on functionality, but also altered core-functionality.</p><p></p><p>When you change programs it is smart to restrict these changes to events and API. This makes it easy to add or change functionality, because API's and events are clear interaction/connection points. The edge://about flag "de-elevate on launch" is such an example of an easy to locate and isolate (program) event/trigger. The same applies for instance to extra functionality "Block unwanted programs" which is clearly related to the "download" trigger/event. The reassuring conclusion seems to be Microsoft made their "core functionality" alterations smartly.</p><p></p><p>For comparison a one man band (Marmaduke at Woolyss) managed in his spare time to de-google Chromium and add some Chrome functionality (existing modules) into Chromium in just 1.5 day. For Microsoft with its huge development team taking more than three days to implement those changes, shows that they may have been changing to much basic functionality code under estimating the effort of regression testing.</p><p></p><p><span style="color: rgb(71, 85, 119)"><strong>Future will tell</strong></span></p></blockquote><p></p>
[QUOTE="Lenny_Fox, post: 858661, member: 82776"] Indecisive: V80 contained many high-risk fixes, so was a major update. Imagine a browser being an user interface with a 'master controller' launching other parts of which the renderer is the most important module. The renderer in its turn processes HTML (the content), CSS (the layout in which content is displayed) and runs the V8 javascript engine (processing the javascript which adds functionality). [B]On the upside (in favor of Edge-chrmium/Microsoft)[/B] In terms of maintenance Opera seems to have the smartest architecture*, so Opera should be able to follow Chrome faster than other chromium based browsers like Brave or Edge-chromium. Microsoft seemed to beat both (Opera and Brave) in terms of adopting this major V80 release *) When comparing Chrome with Opera, you will notice that all the site-permissions are identical and that Opera has an occasional extra flags which they clearly mark as Opera specific, e.g. one general settings for DNS over HTTPS and a Opera-DOH. Opera has neatly limited itself to changes in the GUI and providing bolt-on VPN functionality or modular extra ad-blocker functionality. The build-in ad-blocker seems to use the rule engine of an existing extension, but has its own API and in memory data structure (where rules are stored), which seems to be a simpler version of the current Chrome API (play with advanced ABP-rules and you will notice some things, usually advanced features don't work). [B]On the downside (against Edge-chromium/Microsoft)[/B] When you clone a browser you normally would not touch the renderer and the master controller. When you compare the site-permissions of Edge-chromium with Chrome, you will notice some differences. The same applies for the flags. This indicated that Microsoft did not restrict the changes to the just the GUI or bold-on functionality, but also altered core-functionality. When you change programs it is smart to restrict these changes to events and API. This makes it easy to add or change functionality, because API's and events are clear interaction/connection points. The edge://about flag "de-elevate on launch" is such an example of an easy to locate and isolate (program) event/trigger. The same applies for instance to extra functionality "Block unwanted programs" which is clearly related to the "download" trigger/event. The reassuring conclusion seems to be Microsoft made their "core functionality" alterations smartly. For comparison a one man band (Marmaduke at Woolyss) managed in his spare time to de-google Chromium and add some Chrome functionality (existing modules) into Chromium in just 1.5 day. For Microsoft with its huge development team taking more than three days to implement those changes, shows that they may have been changing to much basic functionality code under estimating the effort of regression testing. [COLOR=rgb(71, 85, 119)][B]Future will tell[/B][/COLOR] [/QUOTE]
Insert quotes…
Verification
Post reply
Top
