In Chrome OS, the browser and the operating system are deeply intertwined. Google cannot update one component without the other, making development a hassle. The company is looking to change that by introducing an uncoupled version of Chrome (nicknamed “Lacros”), which can simplify processes for developers and can even extend the life of Chromebooks. New evidence suggests that Google is getting closer and closer to testing Lacros publicly.
Chrome Story found a feature under development in Chromium Gerrit that adds a flag that allows Google to change the main browser on Chrome OS. One of the last adjustments to the code explains exactly what it intends to achieve:
|
|
|
|
|
|
|
|
|
|
|
The flag will only work when the Lacros browser is activated, which means that the test is only intended to make the decoupled version of Chrome the new standard. It is unclear whether users will be able to see a button to make the switch on their own or whether they will be forced to move at some point with or without their cooperation. Since the flag is not yet active in Chrome Canary, the change will take place in at least a few months, and Google will almost certainly have more to share on the subject long before making these fundamental changes to the operating system.
While it has already become clear that Google is working on integrating Lacros with Chrome OS, this is further proof that the company is moving towards its goal of separating the browser from the operating system. We assume that Google’s move is aimed at keeping Chromebooks safe beyond their end-of-life dates, but Lacros can also help make development simpler, without necessarily extending the life of Chromebooks. However, we’re hopeful about that, especially considering that many schools buy older, cheaper Chromebooks that are nearing the end of their life, quickly becoming a security nightmare.
