I don't get the whole "Let's spend weeks rewriting our build infrastructure to save $240 a year" strategy going on here.
My company has over 3500 engineers. That's almost a million dollars in new spend and you gain basically nothing. It's a product the entire org has already been using for a long time, now you just have to pay a million dollars a year to use it.
I think that's because 2 things are at play here:
1. People are busy and often rarely read past the headline announcing the change, so they are unlikely to know of the caveat.
2. People don't like being taxed at the infrastructure level, so the default price for plumbing tools like Docker is $0. What's the assurance that the $240/yr will not rise to $2400/yr a year later, especially if they fail to hit their revenue numbers? Once the glove comes off, it's so much safer to cap your costs today by seeking out an alternative, rather than be confronted with uncapped costs (or any kind of vendor uncertainty) in the future.
We aren’t even big enough for this to affect us, it is just one more reason for us to look at how we can remove docker from our desktop infrastructure and replace it with something that makes us more efficient.
I had the same frustrations until the other day I saw a tip to enable 'Use the new Virtualization framework' under Preferences -> Experimental Features. Since then Docker's background CPU usage has dropped to 1% and I no longer bother stopping it when I'm not using it.
For people in .gov, that can be waiting a fiscal year to get it in the budget and slogging through paperwork to show that they’re in compliance: