788
Built-in software ‘death dates’ are sending thousands of schools’ Chromebooks to the recycling bin
(www.mercurynews.com)
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.
I would have agreed with that statement until I saw the most recent Technology Connections video about why the incandescent light bulb has planned obsolescence built in. Sometimes it's not malicious but to actually provide a compromise leading to an overall better product.
I don't think software death dates count, tho.
Could you elaborate a bit more on that?
For incandescent lightbulbs, his point was that bulbs can burn fast and bright or low and slow, and standardizing on a lifespan of 1000 hours was a sweet spot between performance and longevity. For example, it makes 60W bulbs from different manufacturers more interchangeable and less prone to tricky marketing gimmicks like a "long life" 60W bulb that's dimmer.
Thank you for explaining this concept. I still don't see how it can be considered planned obsolescence, though. It looks more like a matter of optimizing the output and doing a tradeoff for more performance.
I see planned obsolescence as artificially limiting the longevity or repairability of a product, without any benefit at all, but with the intention of making it less durable. A good example could be locked smartphones without updates.
But perhaps, the definition of planned obsolescence is broader than i think.