@GustavSterbrant Oh for sure. Not discrediting it's usefulness at all. Especially when implemented properly and you're not going on an indirection adventure.
@GustavSterbrant Sometimes people iterate to gain a better understanding of the problem they are trying to solve.
I think it's instrumental to know the constraints of your problem before you make decisions around optimizing it.
But don't leave it for last.
@GustavSterbrant Gonna go off on a limb though: ECS most certainly is not a silver bullet, but it can force people to think about their dependencies and access patterns upfront.
@Matt_Clohessy I remember being jubilant about the community's positive response to 2.0 and while it was seeing better sentiment it was already too late.
@tsoding Agree. The term good code is often conflated with code involving a lot of indirections or abstractions. Not to mention subjective.
Just like it takes empathy to write maintainable code, it takes as much to understand what the code you're reading is doing and why.
The growing complexity of software is not the worst thing. In fact it is completely natural, just as the growing entropy of a system. The worst thing is the people believing it is absolutely necessary and not only refusing to fight it, but actually defending it.