17 ms·
We Need Software Updates Forever
- cable2600 5y agoGood luck finding the people who are willing to support an old operating system forever. Even Linux shuts off older versions from updates.
- linspace 5y agoYou can find lots of instances of people maintaining old software, a lot of times just fans. Nobody is going to maintain anything just for you but we should give the opportunity at least just in case there is enough critical mass. About Linux: is not switching to a new version an update in itself? Maybe your remark would be more correct saying: "older versions don't get fixes". In this case as I said maybe there is enough market, or maybe you have enough money to pay someone to do the job. The problem are proprietary systems that remain closed when going out of business. It's great when at least some of them close but say "here is the code just in case someone wants it, for us it no longer makes monetary sense"
- summm 5y agoBecause manufacturers choose to make a crappy kernel fork with hacky drivers. So it's on them to provide updates to that crap-kernel. If they instead made sure their drivers are in mainline, they could just use official current kernels as updates, and this is how it's meant...
- pantulis 5y agoIf that crap-kernel passed QA tests on its day, what would be the excuse for updating it? The use case does not change, then the crap-kernel is valid. Example: my Korg Kronos is a synthesizer workstation that runs an outdated Linux kernel on an obsolete motherboard. But it just works, it's a musical instrument so why would it need new updates? Security could be arguable (it even has an FTP server, so, yes, but it's a musical keyboard not a server) New features? The product feature set was closed when I bought it. There have been a few updates but basically everything is the same.
- lovelyviking 5y agoWhat do you mean "willing"? Shouldn't they be obligated to? If I pay my own money for the software it should work, no? For how long? Day ? Two? Or may be a week? If so they should say it will work for one week. Otherwise I do not see a reason why it should stop working. If it stops working it's a fraud isn't it? For instance. I have bought iPhone4. Youtube app doesn't work there anymore but all links are redirected to it so basically you cannot see it at all in Safari. Weather doesn't work there anymore. Safari doesn't open many sites anymore. XCode doesn't support it anymore so I couldn't even put my own software there. Transfer of photos to a M1 Mac didn't work last time I've checked. Why it should stop working? They should fix it, no? Or at least provide source code so I could fix it if they do not want to. And this also rises the question of having full access to a device you own, also because those who sell it to you have a tendency to write a garbage software anyway.
- tony-allan 5y agoPerhaps we can just start with updates to the cacerts file so I can still access websites.
- Arainach 5y ago>But even if they fell wholly on the purchaser, consumers would, I suspect, be willing to pay a few dollars more for a gadget if that meant reliable access to software for it—indefinitely The author's premise is entirely wrong, and years of consumer behavior show this. If you offer consumers a $99.99 microwave that will die in 2 years and a $107.99 microwave that will last 5, the VAST majority will buy the cheaper one regardless of the cost per year.
- andi999 5y agoIs this so? How does the consumer know that the slightly pricier one is more durable and not just slightly pricier?
- digisign 5y agoThe warranty should be a clue but is not often advertised.
- laurent92 5y agoI’ve once bought a warranty extension for my washing machine, only to discover that it is impossible to reach them.
- xeyownt 5y agoExactly. Moreover less expensive doesn't mean worst quality. True for clothes, food and electronics.
- muixoozie 5y agorefrigerators. Christ next time I get a fridge KISS is going to be the primary feature I'm looking for.
- andi999 5y agoOnly fancy thing you want is dual compressor, so one compressor for the fridge one for the freezer. (Otherwise they do sometime things like heating one compartment with the lightbulb....)
- hinkley 5y agoCould we agree to a wiring harness for devices that is compatible with some sort of raspberry pi like device, so that worst case we swap in a card running Linux when the caps die in the original PCB? I don’t think we need this eternal support for entertainment systems, but we are transitioning into this same problem set for major appliances and that’s just not a good deal.
- phsource 5y agoI think it's interesting that the author mentions the Playstation Portable as an example: it seems like the reason it doesn't work actually _isn't_ a fault of the device manufacturer: > You might think that a 15-year-old gaming console wouldn't even be operating, but Sony's build quality is such that, with the exception of a very tired lithium-Ion battery, the unit is in perfect condition. It runs but can't connect to modern Wi-Fi without an update, which it can't access without an update to its firmware (a classic catch-22). In this case, developers seem to actually have provided updates, but it just doesn't work! Reminds me of when I booted up an old laptop to find that the old root SSL certificates don't work for sites today and everything's HTTPS now ¯\_(ツ)_/¯ It really points to an issue with net-connected tech (and yes, the PSP actually benefits from being online unlike certain ridiculous IOT devices): really, even if the manufacturer designs with long term support in mind, the rest of the world doesn't. So I don't know quite how tractable a problem this really is in the Internet age; the solution might be just better electronics recycling rather than indefinite updates
- Epskampie 5y agoAlso, doesn’t the PSP use this little disk cartridges? I don’t see why you couldn’t still play those games.
- phoe-krk 5y ago> It runs but can't connect to modern Wi-Fi without an update, which it can't access without an update to its firmware (a classic catch-22). This argument is moot - the PSP is capable of upgrading from its memory card even in complete absence of a WiFi network.
- unwind 5y agoThat is great flexibility and design! Also, it might be possible to either find an older access point, or configure a modern one to use an older standard, so all hope should not be lost. :)
- userbinator 5y agoI've becoming increasingly convinced that this "update culture" is really about encouraging rather than preventing forced obolescence. If they would just make it work right the first time, the way software used to be developed, maybe we wouldn't have this continual update cycle of fixing-and-breaking things every time, but then they wouldn't be able to sell you anything new. Instead, by conditioning the population to accept and even demand continual updates, companies maintain more control over their products and can change them however they want --- which of course can include making them less functional and more user-hostile. It's the same reason why anything "smart" or cloud-dependent is best avoided. For example, all my white goods are several decades old and most of them don't even have any electronics. No, we don't "need software updates forever", despite how much the corporatocracy tries its best to persuade you onto the treadmill.
- Laremere 5y agoI agree that better technology shouldn't need continuous updates, but I do think there are two more likely drivers than planned obsolescence, differing from early technology. Firstly, security. Older devices weren't connected to the entire world with bad actors attempting to exploit anything they can. Until people start writing software that have zero security exploits, anything connected to the internet needs an update path. Secondly, most apps in use today have a server component. Maintaining a perfect backwards compatible server for all clients ever released is a very tall order. Also, I think it's a strong indictment of current OS technology that updates are in question at all. If everything was as modular as it really should be, you'd have the core components of the kernal, the drivers for the hardware bits, (both of which really should be secure and not rely on servers) and then everything else should be in the user's complete control, to update or not as they please.
- selfhoster11 5y agoPeople could just not connect some devices to the wider world. Make them offline, or support airgapped usage patterns, or support a 1:1 connection only with a management interface (like a KVM), or support fully online use but with as simple a protocol as you can to reduce surface area.
- montzark 5y agoPerhaps law needs to be that software needs to be open sourced after some years of product launch or when official support ends - then community can over?
- laurent92 5y agoSame as patent law — After 20 years, no protection? Except the cycle is rather 5 years. As a startup, I’m ok. But customers will be hit by vulns every year, either with the OS or any layer up to my software, and one of them will have to be upgraded.
- deleted 5y ago[deleted]
- watt 5y agoStronger than that. When releasing the gadget, require that the firmware source build tree is put in escrow. After 5 years it is opened to enable ongoing maintenance. The initial release of gadget is released with firmware build by the escrow build process. This will ensure the company actually provides tree that builds the real thing.
- laurent92 5y agoGood idea, better than classic escrow: With a classic escrow, your customers are incentivized to make you go bankrupt, so that they recover the source code and eat your benefits. But that doesn’t solve the vulnerabilities and the need to have 0-day updates.
- alparsla 5y agoIt is tall order to expect companies providing up-to-date code for open sourcing.
- viraptor 5y agoIf we collectively agreed to do it, that's not an issue You provide a copy to a specified organisation which will keep the physical copy locked until date X. If you release something on local market and the source is not deposited, you get fined until you do. It would only need regulation - which of course we won't get due to many companies that would fight this idea.
- danboarder 5y agoFrom the article: "We have seen a global right-to-repair movement emerge from maker communities and start to influence public policy around such things as the availability of spare parts. I'd argue that there should be a parallel right-to-maintain movement." That sounds fine, but the the emphasis is on manufacturer hardware and software support, when the issue really is that devices are locked down. Why not unlock the hardware and publish specs after a few years so people can update their own hardware with new roms, updates, alternative firmware and software, etc. The devs at XDA Developers constantly have to work around these issues trying to support their own old (and new) hardware.
- cryptica 5y agoIn the corporate sphere, software is treated as an ever-evolving amalgamation of code and people - This is why enterprise software services keep changing and breaking over time; without the people, the software stops working. Also, as the people change, the code changes. The code is often overcomplicated; there are a lot of politics going on whereby developers introduce unnecessary complexity into the code as a way to make themselves essential to the company. The code is too tightly coupled with individuals or teams. When some individuals leave or the teams are shuffled around, their code has to be replaced. Also the code is often tightly coupled to specific hardware or operating systems or SaaS services; developers in big corporations rarely bother to try to make their code portable to different cloud providers or operating sytsems. In the open source sphere, software is more often treated as just code. There is not such a strong incentive to play politics because there is no money or job security involved. Because the software often needs to run on a wide range of systems within different cloud providers by different people/companies, on different operating systems with many different execution engines; coupling to specific hardware, systems or SaaS services is strongly discouraged. When open source does become coupled to some external service, it's more likely to be a blockchain - Which has this 'forever' quality (due to the decentralization aspect) and it almost never changes.
- Groxx 5y agoI can't even get replacement parts for my still in production toaster oven, much less things that stopped being produced 3+ years ago. Honestly, I think software has had noticeably better support than hardware - hardware is typically "no" or "here's a different replacement" or "do it yourself (if that's even possible, oh and that voids the warranty)". Software often gets free, easily applied by everyone patches for a couple years or more, and those patches are often available for a decade or longer, even beyond the lifespan of the company, thanks to (sometimes sketchy) alternate hosting sites, which also supply it for free. But to the broader point: I think the cause may be that much of software is built with the intent of it being one-shot. Build to a target as fast as is reasonably possible, then abandon it to do a better job next time. And because there will be numerous flaws with such a quickly-produced thing, make sure to hide your shame, along with hiding your competitive advantage that others can duplicate for free because there is zero material cost. So, broadly, the current status quo makes sense. But yeah, it has downsides. I sure would like open-source everything though. That seems to be the only way out.
- Fragoel2 5y agoSeems to me that this piece comes directly from Magical Christmasland, never taking into account the fact that companies are entities that operate for a profit. Why would they spend resources on maintaining old software when they can just cobble together something that (despite being full of flaws) works well enough that most customers will never complain about? "[...] consumers would, I suspect, be willing to pay a few dollars more for a gadget if that meant reliable access to software for it—indefinitely" Even if customers would be fine with it, I doubt it would work. Not only maintaining multiple pieces of decades-old software is extremely complicated in practice but, mostly, why bother? Instead, companies are more than happy to focus on selling you a shiny new toy every few years. This way they have greater profit margins and the vast majority of customers are totally fine with it.
- GlitchMr 5y ago> It runs but can't connect to modern Wi-Fi without an update, which it can't access without an update to its firmware (a classic catch-22). In this case the issue is that PSP is so old that its hardware simply cannot connect to WPA2 networks (it can connect to WPA and WPA/WPA2 Mixed networks however). This is not something that a software update can fix. Also, honestly, internet access is honestly not very useful for PSP, especially now. Pretty much all games have shutdown their online services, games themselves can be played from Universal Media Disc, and the web browser is pretty much useless with modern web, and with 32MB/64MB of RAM that the console has I don't think Sony could update web browser even if they wanted to.
- toast0 5y agoI thought that the auth happened in the 'supplicant' software, so a WPA capable device, should be WPA2 capable as long as there's enough room for new (and maybe bigger) software and storage of new (and maybe bigger) state. Or does the PSP do the supplication in hardware?
- WA 5y agoIt's very simple, actually: Products that are connected to the internet directly or indirectly need updates forever. Products that are not connected to the internet could keep the same software version.
- viraptor 5y ago> Products that are connected to the internet directly or indirectly need updates forever. Are you prepared to buy that product with the infinite amount of billed work hours included in the price? If not, where do you expect those wages to be paid from?
- selfhoster11 5y agoThat's taken care of by parent's second paragraph - if you're not comfortable with supporting a device indefinitely, make it offline.
- lbriner 5y agoWhat if you want to build a phone handset that you don't want to support forever? It has to be online but there is no realistic way the original hardware will support continuous upgrades, even my Samsung S8, which is hardly ancient, is already slow (for reasons unknown) and will not survive very long.
- viraptor 5y agoYou're basically suggesting no internet or networks, ever. No company will agree to perpetual support of anything. It's not practical or financially viable to do so.
- Twisell 5y agoI was pretty amazed last year to discover that MacOS Catalina finder did perfectly fine job in restoring an early 2000 era iPod Nano once connected through "the dongle of shame" (USB-C/USB-A). Connoisseurs will appreciate that a the time of shipping the device required the now deprecated iTunes software. So someone, bless him, probably took time to port those old firmwares to the new finder based interface. PS: No it doesn't run on iOS 15 but should we realistically expect that ? :P
- imoverclocked 5y agoSo, anyone still use their PDP-8 for email and web browsing? I find myself falling in both pro and anti camps. Old hardware is cool and still useful but the world does incompatibly move on. ASICs are a thing ... and they are often not built with standards that don't-yet-exist. Eg: try running IPv6 on older network gear. Also, hardware tends to get more capable for less power over time which leads to real environmental impact. OTOH: electronic waste is also an impacting problem. "forever" is an impossibly long time in tech... and some tech is definitely made to be cheap and ephemeral. Maybe "we" should start a classification system that gives some idea of the expected lifespan of a piece of technology. At that point, consumers can decide what the worth of a computer is that will be supported (or supportable) for 5,10,15,... years.
- tony-allan 5y agoAt the very least I would want it to be in working condition in a museum. If I owned a PDP-8 I would want to still write software for it as a hobby. It would be a very cool email tool and with a signature "Sent from my PDP-8"!
- imoverclocked 5y agoAgreed! A museum seems like it should be in the condition it was in when the machine was used, not upgraded with a tcp/ip stack and thicknet/ethernet/wifi/whatever. If you are super into this, you could always emulate a PDP-8 on an FPGA, setup some kind of telephony link with a local machine and make an email client with that signature... all the kludge with 1/1000th the energy cost. :) More to the point: A categorization system would be helpful. eg: "this product relies on a cloud service vs this product can work in complete isolation given power and maybe cooling." I would expect a PDP-8 to be solidly in the latter category (works in isolation). I would expect a cheap feature phone has a very limited lifespan because it's filled with mass-produced, cheap circuitry and radios that only work in the context of current standards. Once cell-network technology moves on, those feature phones become useless. Both are reasonable categories to make a device fit into. For the people that want to pay extra for a toaster that is upgradeable or has swappable components, they should be able to find that as a standardized metric or certification. Some people just want a cheap device to plug in and make toast.
- acd 5y agoWhat we need is also open source, open documentation and open firmware. That way when manufacturers loose economic interest in software updates users can take over. Ie open source access should be enforced by law. We also need modular hardware so that processors / main board the brain of the device can be replaced independently of the other hardware. For example the entertainment system software of a car will get much more out of date than the physical hardware of the car itself. For environmental reasons this needs to be addressed. Same with other devices such as TVs the physical screen will last longer than the software in the device.
- lovelyviking 5y agoWe also need to make companies to be obligated to provide source code on demand when they fail to provide a required fix or support.
- Popegaf 5y agoI think introducing a law to require open documentation plus repairability at launch, and open-source+hardware at EOL (maybe even before say 5 years after launch) could work. Businesses keeping their secrets to make a profit and get a head start for a while is OK - it should create competition. Driving pollution with e-waste through forced obsolescence is not.
- advael 5y agoSolutions that mandate companies to continuously actively maintain software can't and won't work. Even if they have to set aside a budget, they could obey the letter of the law and fail to do this, no matter how the law is framed. If we're going to make a mandate, it should be that the firmware for any device you refuse to maintain must be open-sourced and made available to the public. This way, if anyone cares to keep the device running, they can, even if the company goes out of business
- lbriner 5y agoExactly, otherwise it's no different than saying you need to support IE8 because 0.05% of the world still use it. Very unreasonable imho.
- Aditya_07 5y agoUpdate is a necessity in my opinion, but yes it comes with a price and it is really great to see some updates that really take the notch a level up.
- Animats 5y agoOr simple software that Just Works. The Ford Electronic Engine Control IV first appeared in Ford vehicles in the 1980s. It was designed to last for at least 30 years. (I was around when it was being designed.) The program is in a read-only memory etched into the silicon and cannot be changed. It was tested very thoroughly before it shipped by the millions. There are still vehicles on the road with that unit, mostly older Ford trucks. I still have a 1985 Ford Bronco with it. Safety-critical functions should be like that, not in downloadable software.
- KronisLV 5y ago> Safety-critical functions should be like that, not in downloadable software. And then the concept of self driving, driver assists and other functionality comes into play and all of the sudden things are way more muddy - due to the extreme complexity of those, it's inevitable that patches and upgrades will be necessary. > Or simple software that Just Works. That's why you're perhaps spot on here - software should be bulletproof, but achieving that goal might need us to simply do less. However that's not what the industry is striving towards, perhaps apart from aerospace engineering, but even there profit margins have invaded as a metric that's optimized towards. It's unfortunate that it's going to cost many people their lives: https://en.wikipedia.org/wiki/Maneuvering_Characteristics_Augmentation_System https://en.wikipedia.org/wiki/Maneuvering_Characteristics_Au...
- mdasen 5y ago> We should mandate that device manufacturers set aside a portion of the purchase price of a gadget to support ongoing software maintenance, forcing them to budget for a future they'd rather ignore. I think the problem is that any portion of the purchase price will eventually run out over time. Let's say that I purchase a $1,000 phone and the company sets aside $250 for ongoing software maintenance. How much should they budget when? If they spend the money too quickly, it will run out too quickly. But no matter how prudent, it will run out. I think the problem with software is that it's often unmaintainable by the end user. When you buy a house or a car, you don't expect infinite free maintenance of it. You simply expect the ability to have third parties maintain it for a fee. With closed-source software, you don't really have the option to hire a third party to maintain the software for your PSP. However, if we're expecting the original manufacturer to support it for free, that support can't be indefinite. Any amount of the purchase price put away (even 100%) would eventually get exhausted. > Or maybe they aren't ignoring the future so much as trying to manage it by speeding up product obsolescence, because it typically sparks another purchase. I think this is one of the reasons that so many companies have moved to subscription models. If there's ongoing revenue, there's an ongoing reason to support it. Even then, if consumers have moved on, there might not be enough revenue coming in for that device to justify working on it. If there are 12 people who still want to use a PSP and they're paying $10/mo, that won't cover one engineer to keep updating the software. I'm guessing there are more than 12 people who'd like to use a PSP, but you can understand that there is some point at which there aren't enough users even with a subscription model. In a lot of ways, it feels like the author is making two arguments. 1) Companies should provide free updates for their products forever via a single purchase. That strikes me as a weak argument. Nothing lasts forever. Too many things are abandoned too soon and that is a problem - one that could be handled by some more modest proposals like supporting devices for 6 years or something. 2) We should have a right-to-maintain. This is somewhat at odds with the original one. The right-to-repair isn't about free repairs from the manufacturer, but about our ability to maintain our own things (or get third parties to maintain them). Maybe a right-to-maintain could be useful without going the direction of totally free software. It seems like it might be difficult to mandate this, but one could imagine saying that consumers should have access to the source code to make modifications to maintain abandoned systems. However, I think there are issues in general. As more items rely on services that cost money to operate, at some point a device manufacturer will want to stop paying for those services if they're no longer used and for a product they no longer sell. I think it's also important to think about what this means for products that were financially unsuccessful to begin with. When we think of something like the Playstation, we think of something that makes a lot of money for Sony. What about a device that sells poorly and the company has lost a lot of money on the device itself? I'm not talking about some sort of loss-leader where their strategy is to make up the money some other way. I spend $100M creating a new smartphone and I sell 100,000 of them at $500 a piece with a cost-of-goods of $200. I've spent $120M and taken in $50M in revenue. Having to support these devices for decades would mean that companies wouldn't challenge incumbents. I'm not going to go up against Samsung and others if I might get saddled with a huge maintenance burden. You'd only be able to launch a product if you knew that you were going to be able to handle the maintenance burden. That would probably make the market a lot less competitive than it is now. So many companies wouldn't try things for fear of getting saddled with large, ongoing maintenance costs. You'd rather not try your chances at competing with incumbents and consumers would be left with fewer options. I think some of that could be accommodated by tying maintenance to number of units sold or profits achieved. However, that would mean the maintenance window for a product depends on how popular it is. Of course, we already see this a bit in the real world. Companies do maintain popular and profitable products longer than unpopular ones. If we're asking manufacturers to "set aside a portion of the purchase price" then we're giving cheaper and less popular devices less money for maintenance than more expensive devices. That seems to defeat the purpose of buying with the confidence that it'll be maintained. In fact, you'd want to spend your money with large incumbents rather than supporting a new competitor since the incumbent device will likely sell well and be supported longer. I agree that devices should have their software maintained longer. It's one of the things that annoys me so much about the Android ecosystem. I just don't see anything in this article that proposes a workable solution. Free maintenance forever isn't workable and would likely distort the marketplace in other ways with reduced competition since the burden of an unsuccessful product isn't just the immediate losses, but the ongoing maintenance losses. While the author briefly talks about a right-to-maintain, the idea is never actually explored and the article is dominated by the idea of the original manufacturer maintaining things indefinitely rather than us having the ability to maintain our own software. I think a more limited scope proposal might include things like a limited maintenance commitment in established categories where we've seen the lifecycle of devices and such (ex. one could argue for something in the 3-7 year range for smartphones); unlocked boot loaders so that third-party software could be run on hardware; a requirement that key parts of source code be released (even if the release only allows the source and modifications to be run on the original hardware, ie. not free "FOSS" software) if the devices are no longer maintained so that third-parties could offer service for it.
- tony-allan 5y agoOld working devices could last for decades with it's original function or some newer simpler function. For example, I use old phones as clocks. There are a couple of things I would like to see at device end of life: 1. A final update that disables all software related locks so I can load whatever software I want and change any files I want on the device to keep it going. 2. Access to the last version of the developer tools and documentation that can create software for the device, and for those tools to be available on the latest OS or even a frozen virtual machine containing an older OS and apps. 3. Ideally, access to source code or a new software licence that allows decompiling the software.
- fxtentacle 5y agoI predict that this would be circumvented just like environmental cleanup laws are. Your create a new company, release the product, promise the moon. You cash out on the profits of the initial sale. The company goes bankrupt, so sadly you cannot provide support anymore.
- selfhoster11 5y agoProblems with circumvention require better laws, or better law enforcement. The idea is still valid.
- livrem 5y agoWhat we need are stable standards. Eventually. I can understand why internet protocols, (some) file formats, scripting languages, and wifi protocols etc are still in a flux and why everything is a chaotic mess right now. It is difficult to get everything right. Time is needed. But I think there is a lack of discussion about how important standards are as a long-term goal. We need to be able to deploy code that can operate in a stable environment, just like physical objects we design can operate in a world made of natural laws that will not suddenly change around them for no reason (well, rarely change).
- lovelyviking 5y agoWe do not need updates forever. Updates become scary because you never know what BS they decided to add that I never needed which will break things that I did need. We do not need updates forever. We need quality and respect. We need something that 'just works' in the first place and the source code to fix it when it doesn't or when the company isn't there anymore. We need control over our own devices because they become more and more extension of the mind and just like your mind should be protected the extension of it should be protected too. Which means complete control over updates and what they contain. It means full control over each aspect of the device whether it is hardware or software. Updates have became another form of control over your device and your workflow and your life eventually. They have become a tool to push into your throat something you never wanted. They have become a tool to disrespect your choices. If you reject updates they bombard you with endless messages and warnings that jump up in the middle of your work sometimes even breaking your work. Talk about user hostility. Apple for instance abuses even your internet traffic and simply downloads updates without asking and there is no way to turn it off. It is especially "useful" during the travel when you share connection from one device with another and another "thinks" it is wifi so it downloads 5gb of update leaving you without internet access when you need it the most not mentioning the cost. Thanks Apple. You simply cannot turn it off. This is a clear example of disrespect to people and their choices. Asking on their support forum didn't help. Well guess what dear Apple, ignoring people and their requests would not help either. We would bombard you with messages and demands until you start respecting our choices and as long as you bombard us with "invitations to update" without option to turn them off. I think Apple and many others do not realize that pushing something "through the throat" tactic would not work in a long run. We need full control over our devices and the sooner they understand it the better.
- taylodl 5y agoThis is the wrong approach. Rather than "software updates forever" how about when you stop providing updates you must provide that software to the community? The community can maintain it themselves, if they so desire. My solution puts an interesting pressure on companies: if you don't want your trade secrets being released to the public then you have to keep supporting the software. The companies may very well decide that after 10 years they don't care. Which is fine. Now the community can take over. If there's no community to take over then the product is dead and there's no point expending any more effort maintaining the software. Wouldn't this work better and be far more practical?
- cryptonector 5y ago> indefinitely Uh, that's an infinite cost.
- wnoise 5y agoBut with a finite net present cost.
- kabdib 5y agoOkay, that'll be $10,000 per seat, per year, but to get that deal you'll have to reserve the first 100 years. In advance, thanks for your understanding. We'll start breeding the support staff as soon as your check clears.
- nomrom 5y agoThis. Can you imagine factoring the cost of keeping the N95, launched in 2006, updated? All the related software?
- ai_ja_nai 5y agoForever maintenance sounds absurd. "Right-to-maintain" seems much better, like "please, release blueprints and sdks, allowing users to run community powered update systems"
- ai_ja_nai 5y agoI mean, I already wonder what will happen when Square Enix will pull life support to "Rise of the Tomb Raider"'s "endurance mode" servers. A whole game mode made useless. It would be nice if community could patch the game and point it towards different servers maintained by community. Same for PS3 store, why can't I download and run arbitrary software on the console?
- somethoughts 5y agoI wish - for large appliances - where the material weight of the appliance is more than say 95% of the total weight/volume as compared to the electronics PCB, there should be dumb mode feature (either as a brand differentiation marketing feature or a legislated required feature). Note: I actually believe in free markets and believe this could be a huge selling point feature that consumers would pay extra for if marketed correctly as more sustainable. By dumb mode, I mean just a basic non internet connected, 1980's style refrigerator/washer/garage door opener/microwave mode. So you have a smart mode that works until Samsung stops providing smartMicrowave 3.0 updates at which point you can flip a DIP switch on the back and just use it as a plain ol' microwave.
- adolph 5y agoI agree with your point, but the % weight might need adjustment. For example, a PCB the size of an iPhone 13 (146x71mm) [0], weighs maybe 40.61g [1]. The PCB in an iPhone is approx .25 of the surface area [2]. The result is right at 5% of the weight of an iPhone 13. (40.61*.25)/204 = 0.05 0. https://www.apple.com/iphone-13-pro/specs/ https://www.apple.com/iphone-13-pro/specs/ 1. https://www.leiton.de/leiton-tools-weight-calculation.html https://www.leiton.de/leiton-tools-weight-calculation.html 2. https://www.ifixit.com/Teardown/iPhone+12+and+12+Pro+Teardown/137669 https://www.ifixit.com/Teardown/iPhone+12+and+12+Pro+Teardow...
- somethoughts 5y agoYes upon further reflection perhaps its more a rule of thumb than getting to specific weight ratio. Its mostly for manufacturers where the appliances were historically non internet connected (i.e. microwave, fridge) and much of the functionality is not internet related versus a tablet whose sole purpose is connectedness. Its mostly about providing support for a "non-interconnected" UX mode which doesn't bug to create an account with the manufacturers website or even more frustratingly bug you constantly about being unable to access the manufacturer's cloud servers which are no longer being maintained by the manufacturer themselves. And the point of it is perhaps less of a "there should be regulation" and more of a - as an end consumer - might as well post this on a forum where there are likely consumer electronics product managers for said devices viewing comments and getting some gears and mind shifts going.
- OnlyRepliesToBS 5y agowe need fit-for-purpose software more
- gwbas1c 5y agoI'm more in favor of expiration dates with legally-defined minimums. Why? For many of these devices, the developers and teams have long since moved on. If the code was good, it might be possible for an outsider to figure out how to update it. BUT, if the code was poorly-written, it might take a prohibitively long time for an outsider to figure out how to update it. Requiring infinite updates forever just isn't practical. No one will remember how to maintain software forever. But, a clearly communicated (and legally-enforced) expiration date where a company has an obligation to provide updates is practical.
- spoonjim 5y agoIf a company has to provide software updates forever for no revenue, eventually its business model will go upside down. I instead prefer a model where a tax is applied to all IoT sales. Then the manufacturer gets paid monthly out of a fund created by that tax. Then various abuses can be taken out of that fund: appliance support less than 30 years, electronics support less than 15, security or privacy violations, etc. Essentially, IoT companies need to earn their sale price over time.
- agentultra 5y agoThey could release their sources. That would be nice. I'm still getting use out of a Nintendo New 2DS XL thanks to the homebrew community. It's really nice to write software for it thanks to the efforts of talented folks to develop and maintain the toolchains... but the more advanced consoles are getting harder and harder to maintain by design. It's one thing to maintain an NES or DMG-001 but to maintain PSPs and Nintendo Switches once they go out of fashion?
- jedberg 5y agoI don't think companies should be forced to maintain their software forever -- that's too much of an unpredictable burden for the company to bear. Also it's fraught with problems, like what happens if the company goes out of business? But what I do think is they should be forced to release their source code if they no longer want to maintain it. If a server is required for the software, then they should release the server source such that anyone can run one. If there is a hostname that the software connects to, they should be required to push an update that allows you to change that before shutting down the service and releasing the source.
- djur 5y agoYou could have a system of "software trusts" where source code is held in escrow. Businesses and governments could require this in vendor contracts.
- Buttons840 5y agoGood idea. The escrow company should also be in the business of advertising for their clients. "Here is a list of SaaS products you can depend on for the long term" they'd say, and I'd believe them because, worst case, the source code gets released. Whenever I thought something like "I need a finance app" I'd head on over to saasescro.com to see who they recommend. The escrow company could then use this clout to win more customers. We're heading towards a world where there's 20 SaaS apps for everything imaginable (or are we already there?), this could be a competitive edge.
- jandrewrogers 5y agoThis has been common practice for decades.
- Silhouette 5y agoBut what I do think is they should be forced to release their source code if they no longer want to maintain it. This is a common suggestion from open source fans but it quickly fails on practicality. What if the code includes licensed software from a third party? What about trade secrets of the developer, or information provided to them in confidence by a third party? You quickly end up back at software developers either having to maintain indefinitely or accept an onerous set of restrictions and either way the end result is that a lot of software never gets made at all. There is definitely a serious problem with having our modern dependence on software and yet accepting the very limited support that some developers have tried to get away with lately, but I don't think attempts to force the source open are likely to be the solution we need.
- jfrunyon 5y agoSome of the problems that this article mentions (like the PSP not connecting to modern wifi) can't even be addressed by software/firmware updates. The PSP's hardware supports 802.11b and WEP. There is no way to make it support newer 802.11 standards, nor to support WPA2, just like virtually all other hardware which was released before WPA2 existed. Also, the PSP can install firmware updates from game discs, and I believe also from local (USB-accessible) storage.
- sigzero 5y agoWell that is NEVER going to happen.
- VLM 5y agoThe most likely outcome of demanding software support would be the elimination of perpetual software licenses and maybe logic bombs in the hardware to destroy the hardware after a certain calendar date. So buy an iphone in 2023 (or really any hardware), the software license says it'll only work until 2025, after which its illegal to operate all licences revoked and only a 'computer pirate' would illegally try to run an iphone 2023 after 2025, and to enforce that if an onboard real time clock sees a date significantly beyond jan 2025, say... march 2025, it'll fire some FET transistors to crowbar the battery circuit and blow the internal fuse (hopefully thats all that happens LOL...) It'll be greenwash marketed as "making the world safe for those dangerous old lithium batteries". "Help prevent lithium battery fires while also saving the planet, by recycling your old phone every two years" A distant side effect of that will be something like forcing the adoption of something like certificate protected NTP service, because honeypot MITM types might find it hilarious to spoof a coffee shop's wifi, get everyone to connect to their fake network, then emit NTP packets claiming its 2040 thus making all equipment on the network self destruct. Imagine a cheap little $5 raspi level of hardware that can be plugged into any open ethernet port on any enterprise network, determine and take over the local NTP service via some trickery or whatever, then it bricks every piece of enterprise hardware on the LAN, LOL. Maybe it bricks unless the enterprise makes a special payment thats only 10% the hardware cost of all enterprise hardware, LOL... The future is always an exciting time for infosec workers, LOL. "We" already convinced people to replace incandescent lightbulbs that lasted a decade with "LEDs that will last forever" except home depot only sells LED products that are engineered with insufficient heatsinks such that LEDs only last two years, so now people buy new bulbs five times as often as the "bad old days" because they think they are "saving the environment" with LEDs. I'm sure we could pull this off with phones and any other equipment that uses software. Heck, put five cent microcontrollers with RTCs into each LED light bulb to make absolutely certain nobody gets more than two years life out of LED products....
- Silhouette 5y agoSomewhere after right-to-repair comes prohibiting built-in obsolescence and I suspect we'll get there eventually, as environmental awareness among younger generations becomes more influential on consumer spending if not before. But we can bet that plenty of businesses will try to play the kinds of games you're talking about first.
- asasidh 5y agosure, send bill to ieee ?
- victor22 5y agoNot gonna happen, this is not an accident, planned obsolecence is planned across most industries. That said, we do need to buy less crap, and try only to buy stuff that will last.
- li2uR3ce 5y ago> we do need to buy less crap I really wish there was an easy way to do this. Price has largely been decoupled from quality. Reviews are fake. Flaws are not obvious until it's too late. You don't have the right to repair. Warranties are useless. Companies are basically not competing on quality--they're not directly colluding but in effect...
- Voloskaya 5y ago> The devilish details come in decisions about who should bear those costs. But even if they fell wholly on the purchaser, consumers would, I suspect, be willing to pay a few dollars more for a gadget if that meant reliable access to software for it—indefinitely. I think the author has a hard time realizing the cost of what they are asking for. Infinite support is not going to cost just a few dollar more, it will cost, well infinite money. But even if we take "forever" to mean something like 30 years, it's a crazy amount of work that only goes up every year, as finding/retaining someone that knows how the system works becomes harder, and just keeping track with the technological advancement also becomes harder.
- indymike 5y agoI'd be good with disclosing on the package, what date support and updates for my product will end. Then I can make a good decision.
- JohnFen 5y agoAs a user, that's fine by me -- as long as nobody is forced to take an update.
- will_walker 5y agoI wish that manufacturer's had to announce supported software lifetime of a product, that you could compare and contrast on a general spec sheet, like energy efficiency. I also wish that device manufacturers should offer a marginal or low-cost software update service on a yearly subscription fee to ensure the longest lifespan out of a device. Particularly in the case of Sonos, I would be happy to shell out a few bucks a year to keep my older speakers up to date, maybe give us access to Airplay 2 or other standards. How many iPhone camera tricks used to sell the latest model are just computational at this point? I feel like adding a long tail support subscription would really help the economics for B2C device manufacturing while moving us away from the mentality of continuously junking our silicon.
- nephanth 5y agoEven if it cannot connect to the internet, the psp van still run games, can't it? That isn't "useless" in my jargon