3 ms·
I can't help but look at this from the other direction: why does code constantly have to be updated? There's something to be said for something that, once built
by mcv 6y ago
I can't help but look at this from the other direction: why does code constantly have to be updated? There's something to be said for something that, once built, simply works.
People love plenty of old things: antique furniture, oldtimer cars, classic books from centuries ago, monumental buildings. But software needs to be constantly rewritten en updated, and that takes a lot of work.
On the one hand I don't want to make the case for outdated languages and systems, but on the other, we are spending a lot of effort just keeping things up to date with the latest technologies. Sometimes that's really necessary of course; security holes need to be fixed, and frequently new features are necessary. Better ways of doing things have been discovered or developed. But man, there's a lot of effort going into these legacy systems.
Although I love learning new things, I also kinda hope that some day we'll reach systems and languages that are so well-designed that they don't need to be changed much, or at least keeping them up to date will become trivial.
- Cthulhu_ 6y agoIt's because the landscape moves on. Take Windows applications; plenty of apps were built for Windows 95 or Internet Explorer 6, but they no longer work in newer versions of Windows or IE. Companies are holding back on updating their users' browsers because they depend on these applications. This leaves them with two options; invest to have the application updated or rebuilt for modern browsers, or take the risk of outdated and insecure software. I guess it can work with sandboxing and virtualization and the like (how they nowadays keep old mainframe applications working on modern hardware), but it's a patch.
- mcv 6y agoI know why it happens, but I still regret it when that means old things become inaccessible. Old games become unplayable, or websites stop working (not to mention that they are frequently unfindable on search engines), etc. We treasure the writings of the distant past, but the 1990s are already becoming surprisingly inaccessible. For games, there's fortunately gog.com that tries to keep old games playable, and archive.org of course tries to preserve old web content, but that only really works for static content. And then there's all the cool stop-motion lego animation I found before Youtube came along, and now I can't find them anymore. Internet sometimes feels like a city bulldozering their entire city center to rebuild everything according to the latest standards. It's certainly convenient, but you lose so much history. But now I'm talking more about the loss of content than about the fact that everything requires constant updating and is never done. These are two different concerns, but I feel them both.
- nicbou 6y agoYou can build simple things that work forever (or as long as the underlying platform remains backward compatible). It's just rather costly, and most software isn't important enough for that. As the owner of a 40 year old motorcycle, I can assure you that such things also need a lot of maintenance, using increasingly rare parts. Leave it sit for too long and you need to clean the carbs. Even my 2 year old motorcycle needs new oil, brake fluid, tires, brake pads and clutch cables, not to mention insurance, plates and a biannual inspection. Keeping those things on the road is an active job. Of course, objects with few moving parts and no external dependencies will last longer.