Neverware is now part of Google
cloudreadykb.neverware.com
cloudreadykb.neverware.com
They've been working pretty closely with the Google ChromeOS team for a while across the consumer, business, and education markets. This deal may be a way for Google to expand the number of devices running ChromeOS.
Don’t get me wrong: I am a big fan of Arch, but there are a lot of reasons to not prefer it over Ubuntu.
I think I can solve both of those with one stone..!
tl;dr - it's fine to snack on potato chips, but don't expect people to all want to eat the same thing. Variety is powerful.
They don't play AAA games, they don't really do administrative work (and the times they do, Google Drive can help), and they can't really break it even if they tried.
You'd be surprised.
They can (and will):
- install crapware extensions
- allow notifications from random shady sites, which will then make them install more crapware extensions
- change their default search engine (and a lot of data that Chrome sends goes to the default search engine, e.g. keystrokes in the address bar)
It doesn't break the OS per se, but it still results in "my computer has a virus" support calls.
https://cloudreadykb.neverware.com/s/article/Does-CloudReady...
It seems like it could potentially really enable massive reuse of older, slower laptops that might otherwise be thrown away.
It seems to me like handling driver support would be the hard part. Is that their special sauce?
I can't see this as anything but a clear win for the environment and for education. And unlike the "Google shuts down everything" meme, this seems so obviously massively helpful to their entire ChromeOS strategy it looks like it'll be here to stay.
So this acquisition likely means a return to old Chromebooks being ewaste because Google bought out the company that was providing a longer lifecycle.
When Google's team decides a computer is too old to support, do you think their other team is going to be allowed to step in and support it?
Google is likely interested in CloudReady for it's newer uses on Windows PCs, I've seen an employer ship a brand new HP laptop with CloudReady on it instead of the OEM Windows license included. But long term support is likely going to suffer.
I’m having trouble interpreting it myself (see the problem?) but I believe it would go something like “I’ve observed some irony: Google used to have the motto «don’t be evil» and what you describe sounds evil.” Feel free to correct it.
/s
That's called a punchline.
“ Eventually you will initiate support requests directly with Google in the same way that you do for Chrome OS.”
(Full disclosure, I’ve never actually tried to get support for Chrome OS, but I’m fairly confident in assuming it’s right up to Google’s usual support quality standards...)
Congrats: You are lucky and have well placed confidence.
If you go through the user support it doesn't seem to go anywhere. If you then open a chromium bug like a chrome browser developer would, they will say they got no reports on the user channel and then the bug sheriff will eventually close it.
The main thing I hate about modern software development is the failure to understand one source of truth is incompatible with arbitrarily damaging information to fudge numbers. Virtually everything in their database can be correctly marked a duplicate of something they already closed, automatically, possibly without even reading it.
Forgot about it at some point, I'm glad too to see it's still around! Doubt I'd be in tech or so interested in tinkering or programming or whatever if it weren't for that.
I agree with other commenters that Neverware was bought not for old laptops. It is the supposedly zero-administration of Cloudready that in some CXX targetting PowerPoint looks like that old mainframe/terminal setup or like JavaStation (you stick the badge in and your work environment comes up) - CXX like to cut costs through magic of zero-administration/etc. May be Google will even risk to roll it out internally.
It the re-use of old hardware that might be thrown away it's just potential, it's happening at scale right now.
My mother used a Thinkpad T450 with Cloudready for years. To her it was a Chromebook with a larger screen than her old 11" one.
I personally think they will. In a time when many schools are short of money, it makes sense to allow deployment of Chrome OS to existing hardware. Allows Google to expand Chrome OS's base while working within budgets that don't allow for mass purchases of new machines.
For those looking to try Chrome OS on their personal equipment, there's not only Neverware, but there's also the Brunch Project. The Brunch Project uses the official Chrome OS images and provides a way to install them. Neverware sometimes lacked certain features because of their use of Chromium OS, but the Brunch Project avoids that problem by using the official images.
I’m now imagining the announcement to existing support contract users.
“Your account has been migrated to Google’s legendary customer support platform. To receive support, ensure you’re logged in using your paid support email address. Google search will then unlock enhanced Chrome OS problem search mode, allowing you to find other user’s workarounds to your problems! In the event this does not solve your issue, please scream into the void as usual. Our support staff will get back to you never.“
https://discourse.ubuntu.com/t/ubuntu-web-remix/19394
I wouldn't be surprised to see someone attempt a Chrome OS clone at a startup or corporate level. Seems like all the building blocks are there. Someone just needs to assemble it. Simple desktop that revolves around Firefox. With an immutable base system and seamless, invisible-to-the-end-user containers.
Neverware's Chrome OS is a downstream version of the Chrome OS that you get on new Chromebooks.
I do hope that with this acquisition, Neverware's product improves. One chronic problem I have with my pixel chromebook is that I had to disable some security settings to install Neverware's Chrome OS, which causes some problems every time they do an update.
I hated to see it gathering dust in a drawer, so I removed the write-protect screw on the motherboard, blew away the BIOS, and installed a normal BIOS w/ Linux Mint on it. Runs fine. In hindsight I wish I had tracked down the 2015 LS version, since the OG version only has about 4 hours of battery life.
Were you able to get the touch screen working under Linux? How did you install a normal BIOS?
https://mrchromebox.tech/#devices
Be careful when removing the case to get at the write-protect screw, though! Mine was being incredibly stubborn when I tried to get it off, and I unfortunately broke off one of the plastic clips. I was able to get it back on after a few attempts and there's no longer an air-gap between the lid and the board, but I can unfortunately hear the broken clip rattling around when I carry the laptop.
I hope Google does not intend to shut them down.
What to do when they end support...
as it is, you can keep using the old hardware after support ends, you'll just have an outdated browser and linux kernel. In the future, that problem should be reduced to just having an outdated kernel.
With that said though -- yes, if you're into modding or general preservation there are a variety of community spins of Android, and potentially even a small scattering of other Linux-based systems depending on your device.
Now that Android requires the use of a GSI -- or generic system image -- in testing, device compatibility is also significantly better than it used to be. That said, you're still limited to those that support bootloader unlocking. (Notably, while they don't implement this internationally, if you're US-based Samsung is out.) Additionally, GSIs will still have edge cases around drivers (since they don't have to actually work on production devices), Google apps generally have to be loaded separately, and even then the act of opening your bootloader to begin with trips SafetyNet -- which breaks everything from banking apps (for the sensitive-data protections this was originally intended to cover) to Netflix (for DRM) to various games (for anti-cheat) to... Snapchat for some reason?
Where this starts to really get exciting is that, over the next year or two, that requirement for generic image compatibility will be extending to the kernel, on devices that are actually shipping to users. Treble's launch triggered a sort of second wave within the custom ROM scene, as it meant they no longer strictly needed to be ported to devices on an individual basis -- a limitation which up until now has still existed for the kernel.
Some particularly interesting details around this are that a custom kernel is required to run Halium (a GNU compatibility layer for Android devices that allows images like Ubuntu Touch to be loaded as GSIs), and that Android 11 can actually boot on a minimally-patched mainline assuming that all necessary drivers exist.
They're getting axed in a year, two if they're lucky.
I know an acquired company cannot ever say with any certainty or conviction “things won’t change!”, so it’s kinda as honest as I suspect legal has allowed them to be.
If I were responsible for a fleet of Neverware devices, I’d be immediately fast tracking investigations into suitable alternatives and migration plans.
EDIT: Like, it doesn't even have to be a bad thing! Sell it! Go hog with "we're integrating processes to make the product better for users" and "this will let us ship updates faster" and "you'll get more features now that we're an official Google product" (Android support, hopefully). There's no reason to go with this absurd premise that there will be no change (which nobody's going to believe anyways) when you could be saying "yes there will be changes and that's a good thing for you".
Knowing what I have learned over the last couple of years with changes at google ever since Larry page and pichai took over is that the fun is over and money should now be rolling in. And they are hiding the google effect of this acquisition.
In other words, the project is axed. But the enterprise management is cool. And where google will make their money on this bit.
Also we won’t support old hardware because enterprise does not like old hardware. And it stops people from buying better chromebooks.
I've used CloudReady to turn old laptops that would otherwise be junked into Chromebooks, adding years to their life for family members that needed very low maintenance simple laptop like a Chromebook.
It will be a shame environmentally if it becomes harder to rehab old laptops like this in the future.
Imagine, all those upvotes needed to make this a front page article, NONE of those upvoters know what the company is or the context behind it, just that Google did something, so they upvote.
Then you see all these discussion posts about not knowing what it was, and why it's on the front page, etc.
It's basically HN's version of the blind leading the deaf.
I'm one of the people who upvoted this story and am fully aware of Neverware's products. I've actually used their distribution on some old laptops.
I've used cloudready a little bit when I was teaching an introductory class to high school students who I knew all had chromebooks and I wanted to make sure things I was assigning would work on them.
So... Yeah, I kind of feel like you're right.
So it sounds like there is some kind of actual migration plan, even if Neverware itself is getting shut down.
Note: CloudReady Home Edition provides the option to “live boot”, running CloudReady directly from a USB device without installing. Live booting has performance and storage limitations and does not support updates, so we recommend that you only use this method temporary testing.
CloudReady never included Android apps due to licensing issues. A merger could bring Android apps to more devices.
Also, CloudReady added native support for installing Flatpaks, which Chrome OS lacks. I imagine if Chrome OS really wanted that on their roadmap they would have added it already, but it would be a welcome addition to Chrome OS if they merge it from CloudReady.
I CTRL+F'ed through their "about us" page and no mention of Gaiman, either.
Big companies can be come slow-moving risk-adverse creatures that avoid failures by not taking risks.