JavaScript is the web’s CO2.

Lambda 1 Minute

JavaScript is the web’s CO2. We need some of it, but too much puts the entire ecosystem at risk. Those who emit the most are furthest from suffering the consequences — until the ecosystem collapses. The web will not succeed in the markets and form-factors where computing is headed unless we get JS emissions under control.

https://infrequently.org/2018/09/the-developer-experience-bait-and-switch/
Unknown's avatar

Published by John Hardy

Closures are a poor man's object. Objects are a poor man's closure.

Published

5 thoughts on “JavaScript is the web’s CO2.”

  2. Embracing the browser platform and web standards and not trying to reimplement everything in JavaScript would be a start. This is the central weakness of the React model at the moment.

    Like

    Reply

  4. Yes the bubble is still inflating. I think we just have to look forward five years and think about what code will still be running and which code will be looking like legacy. The code with the fewest dependencies and the closest conformance with web standards will have the best longevity I think. That rules out all the major frameworks in use today.

    That’s why I’m concentrating on lightweight custom elements in preference to proprietary component systems.

    Like

    Reply

  5. Having previously done work for State and Commonwealth departments that have a need for accessibility, we always worked under the presumption that javascript should not be needed in order to use a web site. That meant working to standards, 4.01 strict at the time, and if javascript wasn’t available for some reason that the site would still function as needed.

    I think too many focus on and choose the bling over the functional purpose which is to primarily display information in a meaningful way.

    That focus and choice can cause a developer or development team to then rely on a truck load of dependencies of choice in the form of a framework that make their work easier and thus increasing the profit to the individual or business.

    This obviously then leads into maintenance or deprecation of the framework backed site that depends on the knowledge used to implement it which may or may not still be present within the organization responsible for bring it to existence.

    I think the solution that John discussed, essentially getting back to basics, is the key that can be used through the simple action of doing. Do not try to convince others, just do it, leading by example.

    Like

    Reply

Leave a comment