

The way Java is practically written, most of the overhead (read: inefficient slowdown) happens on load time, rather than in the middle of execution. The amount of speedup in hardware since the early 2000s has also definitely made programmers less worried about smaller inefficiencies.
Languages like Python or JavaScript have a lot more overhead while they’re running, and are less well-suited to running a server that needs to respond quickly, but certainly can do the job well enough, if a bit worse compared to something like Java/C++/Rust. I suspect this is basically what they meant by Java being well-suited.
It’s not that there wasn’t any political pressure. It’s that the slightest bit of pressure caused them to pull the plug swiftly.
I think the companies who were led by people personally antagonistic to DEI already weren’t doing it. They started it when the political winds were in favor of DEI, found that it did something beneficial for them that was worth the investment (ultimately, increasing profits, probably through PR) and reaped what they could. But the slightest headwinds caused them to drop it, for lack of confidence it would be worth the continued investment. For others, it was beneficial enough this pressure didn’t change their decisions.
None of this is likely coming from company leaders caring about DEI for some sort of principled reason, just companies who care about only one thing, reassessing the value of DEI in terms of that one thing, $ return on spend. This is a group who needs subtler treatment than the anti-DEI crowd, this is fair weather friends who don’t care. What little we can do is reward those who don’t give in to the slightest push.