Viewing a single comment thread. View all comments

insanok t1_jaq05pw wrote

You know, this is essentially the truth, the plastic shell is one day going to break, the flash memories won't be able to hold a charge and dead sectors will increase with time. Youl might get more SEU as the silicon ages. Capacitors will leak. It definitely is a finite lifetime.

But as Moores law slows down, the processors aren't getting exponentially quicker and memory isn't getting exponentially more dense - an older model doesn't become out dated quite so quickly, and a laptop a generation old perhaps becomes more desirable than it once was.

Framework aren't advocating the last laptop youl ever buy, that would be a little ridiculous- but they are "revolutionising" right to repair for laptop - making parts accessible, replaceable, upgradeable, including the board level drawings I believe. They provide drawings for a case that can be 3d printed for the motherboard to be turned into a desktop. They're attempting to undo the last 30 years of damage done by manufacturers who only want to manufacture for the sake of manufacture.

When your apple macbook battery reaches 1000 power cycles, you get an unblockable popup saying "service required" - until you have the battery replaced at significant markup on what it actually should cost. When the screen suffers "staingate" they charge $900 for a replacement screen, even though an entire new laptop is $1400. When your SSD goes, but because it's a proprietary connector and Apple no longer manufactures that type.. when your laptop is mostly held together with glue and never intended to come apart "no user serviceable components inside"

The computing industry is loaded with manufacturers of Ewaste and this is the problem. A 10/20$ part breaking writes off the entire device leaving no options.

To me, this is what framework is really addressing. E Waste. This is what BIFL really means. It's a well designed product that will stand the test of time because it is either bullet proof, or has a good upgrade/ maintenance path and not just a "one and done"

36