Owen Williams is a freelance writer and developer who thinks about new ways to get the news. He created the fee (HTTPS: //char.gd ), an independent newsletter, and a blog that helps people keep up-to-date with news.
After more than 20 years of struggle for network relevance, Microsoft plans to remove the core architecture of its Internet browser for Chromium.
These are monumental in themselves, and the Internet – both with pleasure and pleasure as expected: Internet Explorer's legacy is finally dead!
But we just learned the full picture, with Microsoft announcing GitHub's move on Thursday, and that's even bigger than we could have dreamed of. Edge will not only use Chromium as a rewarding engine, but Microsoft is actively investing in developing an open-source engine to optimize it for any device it touches.
The screen is the software your browser uses to display webpages. Different conversion engines have different features and features supported by their own parent companies, the largest being currently used by Mozilla, Google, Microsoft, and Apple.
Here's a bit of the company's long, detailed post about why it makes this change:
"We will develop the Microsoft Edge architecture that will allow the distribution of all supported versions of Windows including Windows 7 and Windows 8 as well as Windows 10. We will also target Microsoft Edge to other desktop platforms like MacOS. for end users (better compatibility) and developers (less fragmentation) requires a consistent web platform that is as widely available as possible.To do this, we will use the Chrome app on different platforms along with a change in model to distribute us IE, so the experience and the web platform of Microsoft Edge to become available in all supported operating systems. "
Yes, that's right: not only will Microsoft shift to Chromium as its rewarding engine, it will begin delivering Edge to all supported desktop devices on the planet, and it will begin building it on the Windows web platform.
It is huge industry-wide news and strives to drive the network to a first-rate experience similar to natural application development as well as make a much better experience for a wide range of Internet users who may not have the power over which browser they use.
The web has already swallowed the development of native applications, but is about to get better. Here are some reasons this news is exciting and will open the next chapter on the network:
Web browsers as first-class citizens
One of the biggest problems today is that despite the popularity of Chromium, it is not really good on the resources front: draining the battery, shrinking system resources, and generally playing poorly. This is largely due to the fact that Google and Chromium do not have their own operating system (outside of ChromeOS) and do not get exclusive access to the low-level system APIs that Safari and Edge have enjoyed.
Since Microsoft and Apple historically have their own browsers for the first time, Chromium has always been designed to be worse: the project simply has no platform resources these giants have had, and has always been a layer of development beyond the official browsers of each platform.
This movement changes everything about this equation. Microsoft can use Chromium in Windows and the Edge browser in the core, which means you can embed a premium experience in any Windows-Chromium-based application, and it's carrying it MacOS:
"Outside the Microsoft Edge browser, users of other Windows PC browsers are sometimes inconsistent sets of features and performance / battery life on different device types Some browsers have slower progress to capture new Windows capabilities, such as touch and ARM processors.As you know, we recently started making contributions that provide these types of hardware support to Chromium-based browsers, and we think this approach can be summarized. "
Microsoft essentially states that it will provide the highest class browser, regardless of the platform you are developing, with exactly the same engine on each device. Not only does it plan to optimize Windows for Chromium, it will also share this work by transferring it to ARM-based devices such as the iPhone and ensuring that resources are effective in absolute kernel: operating system level.
But what really matters is what comes from all this work: the absolute best way to build platform applications, on a scale we've never seen before.
The Network as a desktop platform
If you are a company of some size and want to create an application for desktop or laptop users, frankly, the best choice today is Electron. it is not coincidence that Microsoft acquired GitHub, which is happening with a small project called Electron as part of this acquisition.
Very popular applications use Electron under the hood, including Slack, Visual Studio Code, WhatsApp desktop and many others, largely because it's so easy to target several types of systems with one common language underneath.
Today, however, the electron has a serious drawback: it is based on the Chromium browser, which means it is linked to a full copy of each application that uses it on your machine. After Chrome's "Relax" and "Open", for example, two isolated Chromium cases appear, both consuming resources to do the same.
With this change, it's easy to imagine a common Chromium over Windows that can be accessed by any e-user. Such a change would allow electronic applications to be more efficient, stable and more friendly to system resources (especially memory and battery).
Not only that, but also because Microsoft provides technical resources everyone A browser-based browser, electronics-based applications will experience a touch-sensitive experience that will allow console devices to replace laptops.
If Electron was already the prevailing platform of choice despite the huge limitations, this will open a new desktop wave of web-based desktop applications. Why could you build another language at this stage if you can write once and run everywhere?
Web technology is ready for that
Over the years, Microsoft has made many attempts to create frameworks for developers to use, which failed. There were Silverlight, XAML, WPF, Metro, whatever you can think of, but to a large extent every technology has been trying to attract developers into a scale that matters.
Lately, however, Microsoft has joined progressive web applications as its next platform. PWAs are one of the most exciting developments in the network over the years, allowing web-based applications to access many opportunities without the need for an envelope like Electron. They work offline, can send notifications, cache data, etc., as well as many application developers, such as Twitter, have built persuasive, first-rate PWA experiences that also work on Windows.
The ultimate move of power in all this is that Microsoft shows how it is engaged in the Internet as a platform for the future of applications. He wanted developers to build a PWA for Microsoft Store, but now the weight of its resources stays behind the creation of these applications at the home of the operating system, consuming vast amounts of resources to make them great whether you use one in Chrome or in an electronic envelope.
Not only is this the most constructive outcome of all this, it is key to opening the desktop environment for the next generation of web-enabled tools. Writing a personalized targeting app on any device there will disappear, and Microsoft wants to own it as a bet for the future.
The strategic differences are here many different from Apple's, which has largely ignored any feature of the open network that could jeopardize its own dominance. No web-based Safari notifications on iOS, or the ability to run tasks or caching in the background, etc. Marzipan, the next generation of Apple's next-generation application development platform, has essentially iOS applications that are based on Mac.
Microsoft discovers all these platforms that have shit out of the window, saying it just wants to provide a great and consistent way for developers to create applications that work everywhere once written. It sounds good to me, and it changes the game after years of quarreling, which is best to write about the local platform.
As it turns out, the entire network was in the network. I think that in the long run, this is the best horse you should be betting on, especially when web application tools continue to improve so quickly, despite their age.
This is only the beginning
It's still early days, and Microsoft's plans are not yet fully baked, but I'm excited to become a new setting whereby Web-based technology is treated as a first-person operating system provider.
To be clear there you are flaws in this change: the network as a platform narrows into a duopoly of conversion engines, but only with Chromium, Webkit (which is a Chromium version), and Gecko that runs Firefox. The lighter choice is hurting everyone, as Mozilla's Chief Executive Officer pointed out in the publication for the news that did not shrink the words:
"Google is so close to almost complete control over the infrastructure of our online life that it may not be profitable to continue to fight this. […] From the point of view of social, civic and individual empowerment, the transfer of control over a company's main online infrastructure is terrible. "
What is amazing is that this is the right thing to happen, even with Microsoft's long history in web browsers. It was not so long ago that Microsoft was penalized by an antitrust law for forcing Internet Explorer users, but Microsoft has repeatedly shown that it wants to turn a new sheet.
It's true that the smaller choice is bad and can even hurt alternative browsers like Firefox, but it's hard to justify that Microsoft continues to work on building a special browser that nobody wants to use.
This time is different because Chromium is an open-source project with many collaborators, so Microsoft, throwing its weight behind the standard, can actually encourage Better project collaboration rather than leaving it alone to Google.
If you can not beat them, join them and it seems that Microsoft stays on the Internet for long distances.