The place that I worked that had such nice equipment basically did exactly that: you were given your standard issue equipment with virtually zero flexibilityThis sounds to me like a place that grabbed the "what" and missed the "why". The two questions I would want any company I work for to ask are, "Why would our developers want to be productive for us?" and then, "What do they need to be most productive?" in that order. Give me a reason to be productive and then make sure my equipment doesn't hold me back.
The problem is a lot of people skip the first question and jump straight to the second. I personally believe they do that because the second question is quantifiable. The article is called "The Price of (Dev) Happiness: Part One" and it gives a price at the bottom. There is something a manager can put in Excel and show to superiors.
However, the "why" is more nebulous and harder to enact. Change company culture? Might take months, or years if it's even possible. But I can order $6,174 worth of equipment in an afternoon.
And this isn't just a problem in IT or even in business. There is a ton of information out there about how to lose weight. The "what" is easy to find. But people (including myself) are still overweight because they have no compelling "why".
So when I read this article, I read as a description of "what". And I think there needs to be articles about the "what" just like there needs to be information about how to lose weight. However, I am going to try to not let myself be enamored by it when deciding on a new job. I'm looking for the "why" as well.