It was almost a year ago that we discovered the new Chrome OS project called ‘Lacros’. Although the purpose of Lacros was initially unclear, it was clear that Google was somehow weakening the Chrome browser of the Chrome operating system to allow the two software to live harmoniously, yet independent of updates. My first thought was that Lacros could be a method for Chrome to continue getting updates after the end of a device. It will enable users with competent hardware to continue browsing the Internet safely and securely with the latest browser updates.
As it evolved, Lacros turned to something more viable for use in the stable Chrome OS environment. The Chromebook-specific Linux version of Chrome is frequently updated and can now hardly be distinguished from the built-in Chrome browser that has been the core of Chrome OS for over a decade. One of the most recent clues for the future of Lacros on Chrome OS came when the Chrome developer team announced that the Chrome browser would soon move to a four-week update cycle. If Lacros splits the Chrome OS browser, it could theoretically follow the same update schedule as the desktop version of Chrome, while Chrome OS receives feature and security updates as needed or planned by developers. In my humble opinion, this theory was greatly reinforced when CEO Sundar Pichai did not tweet so subtly that it was time to update the browser on his beloved Google Cr-48 Chromebook.
Advertisements
The latest development for Lacros has been unearthed by Dinsan Francis of Chrome Story and gives even more weight to the idea that it could be the standard browser for future Chrome OS builds. The discovery comes in the form of a command labeled “Add feature flag to control the primary browser on Chrome OS.” The description of the flag is a bit vague, but by betraying the comments, it appears that the “primary browser” is indeed Lacros.
Use Lacros Chrome as the primary web browser on Chrome OS. This flag is ignored if Lacros support is disabled.
Chrome storage
This commitment indicates that Lacros, as the primary browser is ignored, has not disabled Lacros support. This is because Lacros was disabled by default. Once this flag lands in the Canary Canal, it may cause Lacros-Chrome to launch when you click on a link that would normally open the original Chrome browser. In addition, another Lacros-related flag appears in the Canary Channel providing PWA support to Lacros. This is an essential piece of the puzzle if Lacros has to handle the current workload of the built-in Chrome browser. After all, a PWA on a Chromebook is simply a beautiful Chrome instance wrapped in a personal skin. All these pieces are as far as I am concerned the nail in the coffin. I truly believe that Lacros will eventually be the default Chrome browser on Chrome OS when it finally makes its official appearance. Stay tuned.
Advertisements