For smaller and internal project, the IDE's of yesteryear required less code and had a smaller learning curve to get decent UI's (and other CRUD features). They

For smaller and internal project, the IDE's of yesteryear required less code and had a smaller learning curve to get decent UI's (and other CRUD features). They sometimes weren't esthetic, but they were practical and got the job done. The current web stacks are bloated, and waste busy work wiring together and debugging different layers. Whenever I point out The Productivity Gap, people say, "Oh but now you have more choice!" True, but that choice has a dear cost. At many orgs too few use apps on phones such that catering to different screen sizes is a wasted effort. Maybe some end users need phone screens, but the operators and clerks behind the data generally don't. I believe we need CRUD-friendly web standards, and more who are willing to say "no" to bloating stacks for every what-if. YAGNI still matters. Modern web stacks shot YAGNI in the back.