4 ms·
Uhh . . . because it's 2023 and no software exists on an island? OSes evolve. Dependencies evolve. Literally everything in industry is constantly changing, b
by psunavy03 3y ago
Uhh . . . because it's 2023 and no software exists on an island? OSes evolve. Dependencies evolve. Literally everything in industry is constantly changing, be it for compliance reasons or because the foundational architecture (language, build pipeline, etc.) is changing. Put software on a shelf and it will rot. "Maintenance mode" is not feasible for any credible corporate application or FOSS project.
- fao_ 3y agoIf you target C+POSIX, uh, yeah. It's entirely possible to be "done" with a project. Likewise, a hell of a lot of SDL1.2 projects will still compile and run fine.
- userbinator 3y agoThat's what the propaganda wants you to think... I have binaries from the early 90s that I still use today (mainly small utilities). Win32 ain't going away. The industry is full of solutions looking for problems. Ignore them and stick to the basics if you want what you do to last.
- deleted 3y ago[deleted]
- Falkon1313 3y ago>"Maintenance mode" is not feasible for any credible corporate application Tell that to the banks, government, and companies still running software older than I am. And for which, on the rare occasions when maintenance is needed, the developers are likely using tools older than I am to do the maintenance. (I'm middle-aged btw.) It's been a nice 23 years since the major Y2K projects, and we've still got 15 more until we really have to hustle on the Y2038 projects.