794
Built-in software ‘death dates’ are sending thousands of schools’ Chromebooks to the recycling bin
(www.mercurynews.com)
this post was submitted on 25 Jul 2023
794 points (100.0% liked)
Technology
37719 readers
115 users here now
A nice place to discuss rumors, happenings, innovations, and challenges in the technology sphere. We also welcome discussions on the intersections of technology and society. If it’s technological news or discussion of technology, it probably belongs here.
Remember the overriding ethos on Beehaw: Be(e) Nice. Each user you encounter here is a person, and should be treated with kindness (even if they’re wrong, or use a Linux distro you don’t like). Personal attacks will not be tolerated.
Subcommunities on Beehaw:
This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
The service life of the devices was known up-front. You can check for yourself the service life dates of every Chrome OS machine here:
https://support.google.com/chrome/a/answer/6220366?hl=en
The correct deployment strategy would be to make a big purchase at the front end of a device's lifecycle and then only replacements from then on out so that you get the most out of every machine. Future capital purchases would be with a new device and termination date.
I think this point is really important, and allow me to go one step further: I work in the public sector of education and purchasing technology is such a complex issue that IT governance has to be involved with decisions like this. That's to say that, without a governing body to review purchases (outside of whoever handles the actual procurement, i.e. funds leaving the bank account), mistakes like this will happen.
We can be upset with planned obsolescence, but there's distinctly a human error here where there wasn't enough research and planning.