But the article argues that this is often just a smokescreen. "The notion here is that somehow these companies are backed into a corner, with no other option than to fire people. And that's just not true. These companies are making a choice. They're deciding that it's faster and cheaper to chuck people overboard and find new ones than it is to retrain them. The economics of cutting rather than training may seem simple, but it's a more complex calculation than most people believe. ... Many of these companies are churning through employees, laying off hundreds on one hand, while trying to hire hundreds more."
[In many cases, legacy applications are the sole reason for the continued use of Server 2003.] Those applications may themselves be unsupported at this point, the company that built them may be out of business or the in-house development team may have been disbanded. Any of those scenarios would make it difficult or even impossible to update the applications' code to run on a newer version of Windows Server. Complicating any move is the fact that many of those applications are 32-bit -- and have been kept on Windows Server 2003 for that reason -- and while Windows Server 2012 R2 offers a compatibility mode to run such applications, it's not foolproof.