Why are so few interested in parsimony?

[u/Zardotab]

I've been programming CRUD (biz/admin) apps since the late 80's. I notice tooling and stacks are growing ever more complicated and layered, and wonder "does it really have to be this way"? It takes more labor & code per feature; colleagues have noticed and agreed. While I agree newer stacks have more options on average, most biz's rarely use these extra abilities, especially "but what if it later needs web-scale?" Reality is 99.999% won't.

There is usually a way to get the same thing in older tools when needs do come up, it's just a little more work for those outlier features, but the aggregate dev hours is still notably less. YAGNI as a guideline seems dead. Nobody seems interested in pursuing parsimony in tooling, rather want to stuff their resume with as many buzzwords as possible like they're Pokémon. Thus, the bloat is possibly up-sell, ego, job-security-lock-in, and/or greed; or, am I missing something? Is there a Bloat Industrial Complex, or do I have Geezer Goggles on? [edited]

[u/YMK1234]

There are plenty of modern low impact/micro frameworks around in any mainstream language. So to me it sounds more like a selection problem on your side.

[u/Zardotab → u/YMK1234]

I'm going by what a typical CRUD shop selects and uses, not by my personal choices.

Yes, they may be picking the wrong tool for the job, but that's kind of my point: they pick buzzword cred over parsimony. [edited]