3 ms·
I agree to a point, but there are harsh realities to this. To name just a few off the top of my head, where there is no choice in whether the userland changes
by jiggawatts 6y ago
I agree to a point, but there are harsh realities to this.
To name just a few off the top of my head, where there is no choice in whether the userland changes or not:
- Cipher suites and crypto protocols changing often end up "cutting off" older applications because they used an embedded SSL library that can't do TLS 1.2. This is required because vulnerabilities are discovered in older protocols and they must be turned off.
- Changes in the CPU instruction sets. For example, it is not possible to run 16-bit Windows binaries in a 64-bit host OS, but there are no 32-bit supported versions of Windows. Even if the majority of the code is 32-bit, a tiny 16-bit component can be a showstopper. I had to support a large (20K concurrent user!) environment that ran a 16-bit DOS application. On Windows 2008 32-bit. In the year 2015. Really.
- I've seen apps that just can't handle high performance CPUs or multiple hardware cores, simply because they were written in an 100MHz single-core era. I've seen all sorts of timing issues, deadlocks, etc. For example, one particular release of World of Warcraft simply couldn't patch the game on 4-core CPUs, because one task would race ahead, time out, and then deadlock the downloader utility. That persisted for about a year, because Blizzard thought it was "okay" to support only 99% of their userbase that had 2-core processors that were common at the time.
- If you app has any external dependencies of any kind, its days are numbered. License servers. Update checkers. Content providers. Cloud services of any kind. Whatever. It's going to be turned off eventually, and the app will stop dead.
- wheybags 6y ago> there are no 32-bit supported versions of Windows Windows 10 has a supported 32 bit version EDIT: It support 16 bit apps too: https://www.groovypost.com/howto/enable-16-bit-application-support-windows-10/ https://www.groovypost.com/howto/enable-16-bit-application-s...
- jiggawatts 6y agoBut there's no server version with 32-bit support, but this application required server components not in the desktop edition.
- yuhong 6y agoThings like this is part of why for example Mozilla collect TLS telemetry in the first place. I think when they disabled TLS 1.0 and 1.1 they look for very low numbers as well. There is a Reddit thread where I mentioned this that used to have NSA conspiracy theories on this exact topic: https://old.reddit.com/r/firefox/comments/fmdlzp/tls_1011_support_will_be_reenabled/ https://old.reddit.com/r/firefox/comments/fmdlzp/tls_1011_su...
- int_19h 6y agoLack of 16-bit DOS support in Win64 is a choice itself. It's not technically impossible, and there are third-party implementations of a 64-bit NTVDM (e.g. http://www.columbia.edu/~em36/ntvdmx64.html http://www.columbia.edu/~em36/ntvdmx64.html).