Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Large organisations don’t buy a single batch of machines then call it a day. If an organisation standardised on Chromebooks because of the support period, they will still need to buy new machines and those won’t get the support period they had expected.
 help



The worst part is that Google does not have full MDM management for Googlebooks out of the box and won't have that until "late 2027". That means these can't even be deployed to enterprise until proper policies and MDM frameworks even get built for the OS.

I see orgs flipping back to Macbook Neos now. Google just handed Apple the education market back on a light blue and green platter.


are you saying google is betraying them unless they sell new chromebooks with 10y chromeOS contracts going forward until the heat death of the universe?

No one here is saying companies need to offer products forever. They do need to honor their commitments made in the past. For purchasers who bought more than two years ago and those who purchase after today, there's no issue. They are getting what was promised prior to their purchase. People who bought in 2024 or before will get 10 years. People who buy tomorrow will get 8 years.

The only issue is for those who purchased Chromebooks in the past two years. They purchased based on a promise of ten years support. Now Google is retroactively clawing back two years of that support. If today Google had announced 2036 as end of support instead of 2034, there'd be no problem.


It’s straight-up false advertising and they should be held accountable.

I would prefer the Microsoft way, where they double the cost every few years with extended support, super duper extended support, and more.

Then when my organization inevitably fucks up the migration we can pay money to bail ourselves out rather than being out of compliance.


Can you quote the part of my comment that you think says that?



Consider applying for YC's Winter 2027 batch! Applications are open till November 2.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: