News for hackers. Stuff that matters.
Re:The Baseline Costs of JavaScript Frameworks by StillBored on Wednesday November 28, 2018 @12:13PM (#18553306)
Yes, we were targeting mobile/tablet devices at the time too (well bolting on to existing code base). For example, the CSS to dynamically swap between a side menu and hamburger button wasn't complex (as well as a few other layout changes we made based on screen size), but getting everything to resize properly had a significant/constant overhead during development. Mostly because any given solution took hours to work out.

The alternative of feeding separate style sheets makes it easier to develop, but much harder to test even with the responsive design buttons in ff/chrome. That is probably also why I haven't seen many web apps that try to do everything with a single set of CSS pages recently.

Re:The Baseline Costs of JavaScript Frameworks by nothis on Wednesday November 28, 2018 @12:33PM (#18553513)
So is it time for "CSS libraries" (pls no, though)?
Re:The Baseline Costs of JavaScript Frameworks by WorldMaker on Wednesday November 28, 2018 @01:01PM (#18553876)
Why do you think so many developers use things like Bootstrap, Foundation, Bourbon, Bulma, etc as starting points and languages like LESS and SASS to keep it modular/readable/maintainable? We've had CSS libraries and frameworks for years now.