They’re not (always) incorrect, they’re simply unnecessarily big-headed and dickish about it.
And the “ant nest” is too insignificant to be a fine example. DoD can offer you big speedups, however in this case, 80% isn’t almost adequate to be worth the discomfort they’re causing upon anybody who needs to handle this code.
Whether the SoA change makes any sense depends upon exactly what you’re making with the information. In this case, sure, they’ve made counting warrior ants much faster, however what if you require to do more than simply count warrior ants? What if, in addition to counting them, you require to do a great deal of serialization and deserialization, or some other operation that, that touches most or all of the fields simultaneously? Now the general gain is minimal and you have actually got less straightforwards code.
The efficiency gain is proportional to how huge the items are and how frequently you just require to handle a couple of little pieces of it at a time. Games do a great deal of that, which is why they benefit highly from DoD. Organization code can be doing a great deal of that, often, however once again it highly depends upon the scenario. The blanket criticism of the stoopid business reasoning developers is misdirected.