As a result of the latest Google announcements, there has been a lot of talk about the Lacros browser. It’s freely available to test so, if you know me, I was all over it. After all, you can’t have too many browsers on your computer! In this case, it’s on the Chromebook.
This is interesting reading – Lacros
Since its beginning with Chromebooks, basically what you saw was the Chrome browser as the interface that let you do everything. Chromebooks have matured over the years and now you can run Linux and Android applications which open up a lot of options for software, particularly browsers. On mine, I do have Opera, Firefox, and Vivaldi Android versions installed and they work fine, if you want to work like you’re on a phone.
At one point, I had installed Firefox on Linux and played around with it. As with the Android applications, it was pokey. Functional, but pokey. There was nothing that actually ran on the ChromeOS. Until I read about Lacros, that is. If you read the link above, you’ll know that the master plan is to uncouple the Chrome browser from the ChromeOS and Lacros will be the answer. Ultimately, I suspect, it will be renamed Chrome and the old Chrome will go away.
Right now, you can install and have both on your Chromebook. It’s kind of cool to have both icons stuck to my shelf.
These are the flags that I used to make it happen.
Just like ChromeOS, there are different channels that you could choose – Stable, Beta, Dev, and Canary, Since it’s all in the testing anyway, I went with Stable.
After setting those flags, I had to restart the computer and ended up with Lacros on the shelf. I started it; and all the extensions that I use had to be logged in again as the web applications like Twitter, Flipboard, etc. Interestingly, Lacros stole all the extensions from Chrome so I now have them all there and nothing if I load the Chrome browser.
I made the switch to Lacros as my default browser on my Chromebook and it works nicely. The theme and all the settings from Chrome came over nicely. Most everything works nicely.
One of the things that I use on Facebook throws an error…
I would have thought that message was reserved for Internet Explorer. The other issue that I’ve noticed so far is that screen redraws are considerably slower than in the Chrome browser.
The version number is the same as the version of Chrome that I use but interestingly, it indicates that an update is available but it doesn’t actually update.
There is a qualifier than it’s “Experimental (alpha-quality)” so I’m sure that will change at some point. You have to smile just a bit at the name of the browser; it’s not called Lacros but is labelled Google Chrome. So, it’s a hint of things to come.
It was fun to play around with something that will be coming sooner or later when it’s deemed to be ready for prime time.
Are you interested enough to try?