![]() ![]() I remember giving it a go at first and wondering what in the world Google was even attempting with this. I tried early builds of LaCrOS and it was very bad. It needs to be good.Įarly on, I was really concerned about all that. Anything less won’t be acceptable on a device that is 100% dependent on the browser, so this whole thing absolutely cannot launch in a beta state. ![]() All that will matter is that it works just as well as the Chrome browser that has been the backbone of Chrome OS usage for over a decade. No one will give a rip that by the time this decoupling happens, it’ll be more than 2 years of tireless work. No one will care about how intricate the work is to make it all happen. No one will care that this is a freaking awesome technology letting a Linux browser run like a native app on Chrome OS. LaCrOS can’t launch in a half-baked state. Account sign in for Chrome OS is handled differently than on Chrome for other desktops and a hundred other tie-ins exist that make this a huge undertaking for the Chrome and Chrome OS teams. PWAs (web apps), SWAs (system-level web apps like Files and Settings), shortcuts, Android app links and sign-in handling all lean on the current version of Chrome to function. Stop for a second and think about what that means, though. With that in place, the Chrome browser on aging Chromebooks should be able to be updated long after Chrome OS stops getting updates, thus letting users keep their devices for longer if they choose. Chrome OS as an operating system can get different features and roll those out when ready instead of being reliant on the Chromebook-specific version of Chrome along the way. Once implemented, the Chrome team can simply focus on fixing Chrome for Linux, Mac OS and Windows and those updates and security patches can all happen at the same time across all systems. Why all this work to pull it off? Well, we assume it will be to lengthen the lifespan of Chromebooks and de-couple Chrome OS updates from Chrome updates in the future. In essence, LaCrOS (Linuix and Chrome OS) is a highly customized container running the Linux version of the Chrome browser on Chrome OS. What we know for sure is LaCrOS won’t be called LaCrOS when it launches and, honestly it might not be called anything at all aside from Chrome. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |