News for hackers. Stuff that matters.
Re:The Baseline Costs of JavaScript Frameworks by agentPrefect on Wednesday November 28, 2018 @12:12PM (#18553300)
> in exchange for paying this cost, you gain maintainability, developer efficiency, and (hopefully) better performance during runtime.

You also gain responsiveness to user interactions, a programmatic way to reason about your application/website & and some animation-sugar if you want. Don't throw the baby out with the bath water simply because people follow trends instead of good design practices.

Re:The Baseline Costs of JavaScript Frameworks by Roboprog on Wednesday November 28, 2018 @06:52PM (#18556825)
And in my case, less Java I have to read or write on the back end :-)

I agree, though - it’s much easier to reason about the data integrity and security when there is a smaller code base on the back end, by virtue of splitting user interface concerns off to a front end code base.

I’ve been programming since the 80s, but I’d rather write FP code in JS than OOP code in Java - so long as I’m not doing anything to make the app work badly for people. So I’ve gravitated towards front end work the last 3 years or so.

Another rant for another time...