The Cost of Javascript

[FrancisChung]

Long but well written, detailed and informative article written by an Engineering Manager for Google Chrome about the true cost of Javascript and what you can do to alleviate some of that cost.
Must read!

https://medium.com/@addyosmani/the-cost-of-javascript-in-2018-7d8950fbb5d4

[thetuningspoon]

For some reason I never really thought about the fact that, with client-side rendering, you are basically sending your entire application over the wire. It's like having to install an app each time you visit a website. Makes me feel more confident in the componentized server-side approach I've been pursuing, which seems to achieve 90% of what the fully client-side approach aims to achieve, without the complexity and overhead. And it still leaves room for plugging in a more progressive framework like Vue for the cases when you need that extra 10% of interactivity.

[LostKobrakai]

I've read that one a few weeks ago and while I like the gist of it I find it horrible that the javascript community just seems to replace complexity with even more complexity. Also such blog posts always seem to be about the technical side of keeping js in check, while I feel the biggest gains can be archived by actually doing less in javascript. I'd like to see some practical advice on how to not blow through kb's of npm packages and still having a reasonable interactive website. Yesterday I tried out shopifys draggable library and even that one alone is like a third of the max. size of bundle mentioned in the article – just for drag and drop

[thetuningspoon]

I find it ironic that a product called "webpack" is now touting the advantages "code-splitting"?

It's like we're adding layer on top of layer of complexity just to get back to where we started.

[Soma]

20+ year of web dev and we still on this bs. Best thing that happened is: box-sizing: border-box;  Jees, we fly to the mars...