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 have preordered a framework laptop which will run Linux until it fucking blows up or falls apart.
Enough with being screwed over by well known brands whose interest is just selling you more and more stuff.
Good, maybe that will get them to stop using Chrome OS in schools, it has been a disaster for computer literacy in general.
These things are such junk - even when new they were so slow and bloated that they couldn't load my kid's schoolwork half the time. I had to make sure he had an alternate laptop for use so he wouldn't fall behind. I felt really bad for the school district, it was clear they were being ripped off, and that most of the machines were going to be in a landfill within 3 years time.
When I was in 9th grade it was netbooks with Windows 7 and they were also terrible and fated for the recycling bin before I was a junior.
In most enterprise IT your lifespan for hardware is between 5 and 7 years maybe 10 for printers and network switches.
I'm sure most schools try to stretch hardware as far as it will go but IT would have known when they bought the Chromebooks that they'd not be long for this world as cheap as they were and that's the price they would pay for paying such a low price.
I think what is sticking up the works is on an administrative level, higher ups are expecting IT departments to stretch EOL dates like they used to do with Windows machines but now they absolutely can't and Admin didn't plan to have to buy all new whether or not IT did
Hey Mike Judge should make a movie about this
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.