Google splits Chrome from Chrome OS
Probably the largest change in its history to Chrome OS. It's a lot, this is what you have to know
You may have invested a lot of money on buying your Chromebook, and your Chromebook informs you that it is not updated – leaving your computer exposed to security vulnerabilities and ignoring cool new features in Chrome.
Thanks to an ambitious project called Lacros internally, your upgrade issues will soon be a thing of the past.
Device updates were a big Android issue. In October 2017, the distribution of Android was abysmal — the latest OS version of the phone ran embarrassingly 0.2%.
Although Android fragmentation plagues many devices today through OEM complacency, Google's Treble Project has made a significant difference in raising and extending the lifespan of Android to older devices. Google wants Chromebooks to do the same now, and Lacros is their response.
Lacros is an experimental Chrome binary separator on Chrome OS from device user interface (Ash, Overview Mode, Shelf, etc.). To begin with, developers of Chrome renamed Chrome 's current binary on Chrome OS to ash-chrome. They took the Chrome Linux version, rename it into a lacros-crome framework, improved its Wayland support and architecture, and converted the latter into a Chrome OS operational system. For example, Chrome OS can run on OS 87, but version 89 may run on Chrome binary.
Thus it's cool and all to have two separate Chrome instances side by side, but you may wonder why it's so necessary. We first need to look at how Google changes Chrome OS in order to address this query.
Presently, Chrome has a profound interconnection with Chrome OS, so Google has a monolithic kit to compile and ship to upgrade channels. Although this is not a question, when a Chromebook comes to an AUE or an end of life, the big problem is. As on an Android phone, you miss out on latest Chrome OS updates when your Chromebook hits AUE.
Losing a Chrome OS update also ensures that Chrome does not upgrade itself either, leaving the browser obsolete, unreliable, and unable to benefit from new services on the web.
Google 's reaction to this may be Lacros. Since this Chrome binary is separately distributed from Chrome OS, Google is able to update the Chrome binary easily independently of the OS. And if your Chromebook hits AUE, at least your browser receives the new and most relevant updates from Google – and importantly, security improvements. This can have a major positive effect on the educational climate if you think about it. Schools buy huge numbers of older Chromebooks to students , particularly now with many virtual classes during the pandemic.
Lacros allows school Chromebooks to continue receiving Chrome updates by reaching AUE, allowing students to continue using their Web based platforms. Institutions will no longer have to purchase a new range of revised Chromebooks, which could save considerable money.
What Google is going to take with Lacros is not obvious. For instance, no information is available about how Lacros is being implemented about Chrome OS when this feature is being implemented on Stable channel. I assume that Google will create Chrome OS to allow users, once their Chromebook reaches AUE, to install Lacros, but I am not positive. I'm excitable to see Google attempt to extend the life of Chromebooks. Lagros is shaping itself to be an exciting project.