|
|
|
|
|
|
by rbranson
5708 days ago
|
|
|
Honestly I think Microsoft's extreme desire to maintain backwards compatibility has hurt developers in the long run. That's an awful lot of legacy to carry around and they haven't been proficient at phasing products and platforms out when they're clearly way beyond their prime. They should focus more on being innovative and having solid strategies for moving developers incrementally towards new platforms and frameworks. |
|
|
I currently contract for a company with 50,000 + employees and some pretty specialized software that way too many people need to access. Getting that to change is like turning a convoy of sea liners with no radio communication.
The programmers who actually understand the weird ass domain of that software really wish they were still writing COBOL on a mainframe, the users who know how to use the software are understandably reluctant to have to learn another application when the existing works fine for THEIR needs (and job security). We have succeeded in getting a lot of stuff transferred to Citrix servers, but there are still a few hold outs / problem areas.
So, yeah, sometimes we really need the existing old stuff to still work.