4 ms·
Containers on the desktop are a symptom of disease in much the way that a fever is a symptom of disease. Fevers mitigate viral replication efficiency. Container
by superkuh 3y ago
Containers on the desktop are a symptom of disease in much the way that a fever is a symptom of disease. Fevers mitigate viral replication efficiency. Containers on the desktop mitigate future shock from the underlying libraries changing so fast that software written at T+3 years cannot be compiled or run on system libs from T+0 years. Like a fever they cause lots of other problems that damage the system but at least preserve most functionality.
The accepted pace of churn in software has now shrunk below the release cycle rate of operating systems. The problem is caused by developer's obsession with the bleeding edge, not being lazy. But it's not just devs. These days if you haven't made a change in your software in the last year people will start asking if it's no longer developed. The eternal wave of now has to be surfed and stability is just a dream from the past.
- lylejantzi3rd 3y ago> It's caused by developers obsession with the bleeding edge, not being lazy. Exactly. If developers really were lazy, the libraries wouldn't change as fast as they do.
- taeric 3y agoIsh. Stability of API takes a lot more effort than Rambo engineering.
- Dalewyn 3y agoDaily reminder that Microsoft's devotion to backwards compatibility in Windows is legendary.
- cedilla 3y agoAs legendary as it is overstated. It's excellent for many common software, but for most specialty software, it's often lacking. Despite all the decades of cruft still supported by current Windows, especially 32 bit editions, there are still tons and tons of XPs and Server 2008s and NT boxes in the wild just to support software that would otherwise break.
- seba_dos1 3y agoYeah; and Wine is better at running many older games than Windows is.