A new experimental flag to make Lacros the primary browser on a Chromebook was found this week. Chrome Story reports that the flag isn’t yet available but should be soon, at least in the Canary Channel. Before you search for the flag to enable it once it arrives, it’s work taking a look at Lacros vs Chrome and Chrome OS on Chromebooks.
What is Lacros?
If you haven’t heard of it before, Lacros is a standalone browser that runs on Chrome OS, and therefore, on Chromebooks.
That may sound odd because Chrome is the default way to browse the web on these devices. But it makes more sense when you realize that LaCrOS is essentially the Linux version of Chrome.
That means it offers the same experience as running Chrome on a Linux desktop or laptop. And it means that Google can make good on its promise to decouple the Chrome browser from ChromeOS. At some point, Lacros will be the default or primary browser on Chromebooks.
Google’s own documents on Lacros spell this out:
Lacros is an architecture project to decouple the Chrome browser from the Chrome OS window manager and system UI. The name comes from Linux And ChRome OS.
It’s likely that you won’t even notice during most activities other than configuring different settings on your device. Once Lacros is generally available, you’ll configure browser-specific settings in the browser and Chrome OS settings in the current Settings app. There’s even a link in the Lacros settings to the Chrome OS settings to remind of you this.
Why is Google doing this?
Simply put, by decoupling the browser from Chrome OS, Google gains some logistical advantages.
As Chrome OS stands today, any Chrome browser updates for new features, bug fixes, or security reasons, must be integrated into a Chrome OS release. That adds complexity since Chrome OS itself is changing every six weeks or so. Some of the browser bits might impact Chrome OS or block upcoming features. So this model isn’t efficient.
Once the browser is separate from the operating system, efficiencies are gained. Google can push browser-only updates to Chromebooks at any time, just as it does for Chrome on Windows, macOS, and Linux.
Additionally, this will enable Chromebooks to run different versions of Chrome OS and the browser, again, per the official documentation.
This could potentially extend the life of some older Chromebooks that are beyond their Chrome OS support expiration date. While the operating system wouldn’t receive updates, the browser could. And that would support safer browsing on such devices. I personally don’t think that’s Google’s long-term strategy but I could be wrong. My thought is that the Neverware purchase has a better chance of delivering more updates to older devices.
Can I try Lacros now?
In short, yes.
However, the Lacros browser isn’t enabled by default and won’t likely be for some time. I say that because when looking at code commits and comments for the new Lacros primary browser flag, I noticed that there specifically hasn’t been a target release date for Lacros.
Indeed, the current flag to use Lacros at all isn’t set to expire until Chrome OS 98, which is at least 6 to 9 months away.
Still, you can try the browser now. Simply head over to chrome://flags/#lacros-support to enable it. Once you restart your browser, you’ll see a second browser icon.
Lacros is in yellow, while your standard Chrome icon is multicolored. You can run instances of both at the same time as they’re completely separate applications. You can also sign in with your Google account and have your browser settings synchronize over.
Will there be a real difference between Chrome and Lacros on Chrome OS?
As I mentioned, most people won’t really experience a difference once Lacros is the one and only browser on Chrome OS, aside from the settings. All Chrome functionality on a Chromebook should be the same at that point. However, this is also the reason Lacros isn’t yet the default browser on Chromebooks.
There are tons of APIs and hooks between the Chrome browser and the Chrome OS system. Google is essentially rebuilding those into Lacros, and even changing up some of the rendering methods. That kind of effort takes time to make and test all of the changes. And it’s particularly challenging as Chrome OS itself is a moving target with new stable releases every 6 weeks.
In the end, however, end users won’t be radically affected. Lacros will likely be called “Chrome” instead of the project code name. The browser icon will look just like the current Chrome browser once the transition is over and we’ll go from two native browsers back to one.
Of course, you can still download other browsers using the Linux container on a supported Chromebook. That won’t change. You can install Brave, Firefox or whatever you want to browse the web as long as it has Linux support. Just remember that any alternative browser won’t be your default or native browser on a Chromebook.
12 thoughts on “Lacros vs Chrome and Chrome OS on Chromebooks”
Sounds pretty good! Anything that expands the “updates-life” is ok by me.
Wonder if they will still keep the Chrome OS Chrome going alongside? !?!? lol
Chrome only got / gets 2 ish years of extra updates on Win 7 (pandemic changed this) after Microsoft stopped supporting it. So I would only expect the same on Chromebooks. Good but not amazing.
What is performance like given it’s a Linux app (containers etc or however it works) ? Might actually slow some Chromebooks down ??
If they can do this with Linux Chrome surely all Linux apps could come this way rather than Linux beta, i.e bit more user friendly with its own play store section??!!?
Off course techies will like ability that user profiles from Linux Chrome will bring, very cool indeed.
It’s actually a native app built on top of Linux, just like the current browser is in Chrome OS. No VM or containers involved. I’d expect little if any, noticeable performance difference. I don’t forsee Google bringing native Linux apps to Chrome OS without a VM or container for security reasons.
Questions come to mind:
1) Is the plan for Lacros on stable Chrome OS to continue to run in a Linux application container, which would mean that non-Linux users would potentially have to enable Linux?
2) If the plan is for Lacros to be adapted to run as a pure Chrome app, could others also decide to port the Linux version of their Web browser applications to run as pure Chrome apps.
3) After the extraction of Chrome browser from Chrome OS, would loading Lacros be mandatory for the OS, or could, say, an Android browser app be the only installed Chrome OS browser?
Good questions, as always. As far as the first, Lacros doesn’t run in a Linux application container from what I can see. I’m running Lacros on a Chromebook that doesn’t even have Linux enabled. For the second, I assume devs can do that now, i.e.; progressive web apps. Lastly, I’m not sure. But I don’t anticipate Google ever offering Chrome OS without a desktop browser. Lacros will (from all evidence so far) basically become the default browser on Chrome OS devices. Any additional browsers installed would be that: additional browsers.
Scrolling is not as fast and smooth on Lacros as on native Chrome OS browser. You can see the difference by scrolling up and down rapidly. In native browser, the web page moves with your fingers no matter how fast you move them, not so with Lacros, which lags.
As a long time Linux user, hardware acceleration is very hit and miss and I’ve seen it implemented in full in a Linux web browser. From what I understand this is due to the old display server (called X or X11) is archaic and developers find it very hard to work with and the new display server (called Wayland as mentioned above) being relatively new and unpolished. It makes sense that others have noticed the ChromeOS Chrome being smoother and faster right now.
^ That was meant to say “and I’ve ‘never’ seen it implemented in full” above.
The ideal thing here would be to use this flag/switch to make Firefox your default browser on ChromeOS, and avoid any Chromium-based browsers.
Because… it’s in the name: Senile. He only remembers way back when Firefox was a great browser (the best, in fact). Mozilla prioritized user productivity back then; Mozilla cared about what users wanted back then. Then Mozilla lost its marbles (marbles made from XUL). I wish I could use that old Firefox browser, too… but Firefox now ain’t what it used to be–literally. Vivaldi is the new Firefox (or at least as close to it as possible). Still, on a Chromebook I’ll stick with Chrome. Again, it’s in the name.
Hey thanks for this information. I have a Samsung Chromebook 3 that no longer receives updates and I installed this Lacros and seems to run fine so I have two questions:
1- Can I uninstall Chrome so that memory is not so full?
2- Does Lacros autoupdate and I will no longer hve security risks as long as my Chromebook still works fine¿
Thanks in advance.