This is a major beef I have with many modern frameworks - many confuse verbosity with simplicity or ease. Conceptual complexity is of enormous importance to th

This is a major beef I have with many modern frameworks - many confuse verbosity with simplicity or ease. Conceptual complexity is of enormous importance to the usability of a tool. I build APIs for a living and have often needed to push back vociferously over things that would make code terser, but the underlying mechanisms harder to understand. That said, I actually think codegens are often the right tool for the job - it removes a lot of boilerplate (at least from the developer needing to write it) but doesn't obfuscate underlying mechanisms - those are free for examination as needed. Of course, the devil's in the details - if the codegen'ed stuff is pure spaghetti that defeats this benefit. The worst, worst sin of all are frameworks that insert "magic" functionality. For example: name a thing in a special way and stuff will automagically happen to it? I can't think of a worse, more opaque way to design a system than rote memorization of incantation that reveal nothing about what's actually happening.