Like many people, I raised an eyebrow when I heard that Microsoft was killing off Internet Explorer in favor of what was then being touted as Project Spartan. And, like many people, I was pleasantly surprised to hear that the Microsoft Edge (as the project later became) was actually a half-decent browser. Aside from the fact that it was both lightweight and fast, for me one of the more interesting aspects of Edge was its excellent ES6 compatibility. At last it seemed that Microsoft was doing something right in the browser space.
So, it was with some interest and indeed confusion, that last week I read that Microsoft had released an open-source browser, built using HTML, JavaScript, and CSS. Was this going to be a competitor to Edge? Was this intended to address the fact that Edge only ran on Windows devices? Would it be yet another browser to support? And most importantly, since when could you create a browser using just HTML, JavaScript, and CSS??
So many questions. The fact that Microsoft were calling their new creation âJavaScript browserâ, just made me want to find out more.
Some quick research showed that, in keeping with the new Microsoft, the source code for this project is available on GitHub. The projectâs README is very informative and states that this new browser is a proof-of-concept app, designed to demonstrate the capabilities of the Windows 10 platform. It is built around the HTML WebView control and uses primarily JavaScript to âlight up the user interfaceâ.
It goes on to detail how theyâre taking advantage of the new ECMAScript 2015 support in Chakra, the JavaScript engine behind Microsoft Edge and the WebView control, to remove a lot of the scaffolding and boilerplate code which makes a project like this possible. Hats off, Microsoft!
But what do you think? Are there any Windows 10 users reading this? Have you taken this browser for your spin? And what are your impressions of the platform as a whole?
I must admit, Iâm an ardent Linux user, but itâs things like this that make me want to give Windows another try.
This editorial appears in this weekâs issue of the SitePoint JavaScript Newsletter.