4 ms·
>Legacy systems and architectures can’t be around forever. Why not? The bits don't decay.. Yes, this leads to an architectural mess, but I'm talking about a c
by jhallenworld 3y ago
>Legacy systems and architectures can’t be around forever.
Why not? The bits don't decay.. Yes, this leads to an architectural mess, but I'm talking about a competitive business advantage.
- manuelabeledo 3y ago> Why not? > Yes, this leads to an architectural mess Right there. There's no notable advantage in supporting a very small minority of the applications out there, at the cost of keeping units useless for the 99%.
- bear8642 3y ago> There's no notable advantage... Potentially one if a large customer's paying you for it. At work, I'm helping a client upgrade from a decade old version (v12) of our product and having to copy over the switches to keep the even older (v11 and previous) behaviours
- manuelabeledo 3y agoTen years ago was 14 years after the introduction of the x86 64-bit instruction set, and 28 years after x86-32. I’m quite sure we will be OK without support for 16-bit instructions.