\nWhy is this updates-schedule change for these Chromebooks odd?
\nNow, Google has made changes to Chrome OS in the past to extend the viability of the platform. Most recently, it revealed that some Chromebooks would receive up to eight years of updates. That includes some notable entries such as the Samsung Galaxy Chromebook, Lenovo 10E Chromebook Tablet, and the Acer Chromebook 712.
\nWith the two Chromebooks above scheduled to hit their end-of-life (EoL) date in June 2029, though, Google has gone beyond that. But not quite by a year. That represents a fragmentation of the company’s approach to its devices. Namely, it’s just another big jump away from its fixed life expectancy for the devices. And that’s already a difficult timeframe to determine in many cases. Although many Chromebooks now mention EoL in settings under „About Chrome OS.”
\nIn fact, that’s the second such fragmentation since not every Chrome laptop will receive the eight-year cycle either. Instead, most last between five and six years from their announcement. Not from the purchase or from when they hit store shelves. So there are, in effect, three different classes of Chromebook now, split by the update cycle. That’s atop the different classes that already exist for students, Enterprise, and general consumers \u2014 as well as splits in value and pricing.
\nIs Google going to collect itself and bring things back to uniformity?
\nOf course, updating Enterprise Chromebooks to last longer does arguably make sense. Those are the devices typically used by schools and businesses. So adding value helps Google grow the primary market for those devices. But the lack of uniformity could also spell confusion for some users. And it remains to be seen if the eight or nearly nine-year update cycle will be brought to the platform as a whole.
\nThe post Google Seems Confused About How Long Chromebooks Should Get Updates appeared first on Android Headlines.
\n
![](\"https:\/\/plus.maciejpiasecki.info\/wp-content\/uploads\/2020\/10\/Boxed-Chromebook-Logo-DG-AH-2020.jpg\"){kind=logo}
\nSource: ndroidheadlines.com <\/p>\n","protected":false},"excerpt":{"rendered":"