One of the criticisms of Javascript developers is that they make things slow with bad practices and by adding needless frameworks to their apps. Then in order to solve that problem, they bolt additional frameworks on top to do complicated, hard-to-debug compilation steps, or to optimize specific code paths, or to defer loading to make things appear faster than they are.

What they don't realize is that all of the bloat in their apps came from things that seemed like good ideas at the time. If they were actually smart enough to engineer their way out of the problem, they would have also been smart enough not to engineer their way into it in the first place. So when they add their new speed-solutions on top of the existing codebase, often they introduce new bugs or limitations that end up making their app even worse in the long run.

Wherever possible, a solution should not be significantly more complicated than the problem. Occasionally, you can get genuine speedups from adding new libraries, but this should not be treated as the norm. Usually, the best way to make apps faster and lighter is to stop using so much stuff.

And as it is with Javascript, so too is it with climate change and geo-engineering projects.