You joke, but it really is more work. Iv'e developed software in languages from assembly language to JavaScript, and for any given functionality it's been easier to write it in RISC assembly language running directly than to get something working reliably in JavaScript running on a framework in an interpreter in a VM in a web browser, where it's impossible to reliably know what a call is going to do, because everything is undocumented and untested.

One of the co-signers of the Agile Manifesto had previously stated that "The best way to get the right answer on the Internet is not to ask a question; it's to post the wrong answer." (https://en.wikipedia.org/w/index.php?title=Ward_Cunningham#L...) I'm convinced that the Agile Manifesto was an attempt to make an internet post of the most-wrong way to manage a software projects, in hopes someone would correct it with the right answer, but instead it was adopted as-is.

Even with older lower level languages like C and COBOL '02 it's easier to do simple things like find a file, read the file, and draw the file on the screen as a raster image using a resizable canvas than it is to write the JavaScript to do the same thing.

The mangling of JavaScript to fit through every hole seems to be the biggest mistake made in modern programming, and I'm not sure what even keeps it going aside from momentum. At first it regained ground because Flash was going EOL, but now?

What makes Agile the most-wrong way to manage, in your opinion? I'm curious.

What’s the most complex thing you wrote in RISC assembly?