author: Bart Swiatek
Microsoft Edge on Chromium Engine is Open for Testing
Microsoft has released an early version of the new Edge browser. The program abandons the EdgeHTML engine in favor of the popular Chromium technology.
Microsoft has released an early version of the new Edge browser. Unlike the previous builds, the current one is based on the Chromium engine (just like Chrome or Opera), not EdgeHTML. It is worth noting that the program is intended for testing - users should expect errors and other problems. It is also not recommended to use this browser for tasks where stability and security are important, such as work or online banking.
If you still want to try out a new work by Microsoft programmers, please go to this address and choose one of the two available test builds. In the case of Cannary Channel, you will receive an application that will be updated daily - which means that it will be the most up-to-date, but potentially also the most unstable. Option number two - Dev Channel - involves weekly updates and is probably a slightly safer choice. Over time, the developers will also release a beta version, which will be improved once every month and a half.
The browser is quite easy to use and in many ways it resembles Chrome - as in the case of Google's browser, you can find all the necessary settings in the menu that opens when you click the three dots sign in the upper right corner of the screen (except that in the case of Edge dots are horizontal). It is possible to import data (e.g. bookmarks) from other browsers. The program also supports extensions, although reaching them is currently a bit complicated (after selecting the appropriate tab in the menu you can not use the search engine - instead you have to click the "Get extensions from Microsoft Store" option and manually search for add-ons in the right category in the store).
It is worth noting that only Windows 10 users can try the new version of Microsoft Edge for the time being. If you want to learn more about the browser, we encourage you to read the relevant developer blog note.