Comment by tipiirai

> "JavaScript mixed together" and "Strict separation of concerns" is just comparing apples with oranges

I feel this this comparison reveals how deeply framework thinking has shaped our understanding of web development and how thoroughly we've accepted JavaScript monoliths as normal.

Why have we normalized a world where marketing pages need a JavaScript monolith with mixed content? Why do we consider utility classes more "maintainable" than systematic design? Why must every solution flow through JavaScript when browsers provide these capabilities natively?

I have tremendous troubles explaining these things to engineers, who constantly turn the discussion into technical, low-level details instead of looking at the bigger picture. Any suggestions how I should approach this? Thanks in advance!