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?
COBOL is a high-level language, and on the higher end to boot, with support for object oriented programming being added over 20 years go. C is also high level, but the joke is that it "combines all the elegance and power of assembly language with all the readability and maintainability of assembly language". (http://catb.org/jargon/html/C/C.html)
Anyway, C doesn't support any of those things you mentioned, or even functionality as basic as memory allocation, but what it does have is a user-base that so consistently uses the same library for most functionality that it has earned its moniker as the "C standard library" and it's usually conflated with the language itself.
JavaScript, on the other hand, has more frameworks than there are programming languages in common use.
It's not even ambiguous; JavaScript uses syntax inherited from C, so if you can program in JavaScript, you can program in C, where you get a performant, stable, and simple standard library, instead of the framework-of-the-month club in JavaScript.
I think the poster was partly being facetious about being corrected on the internet.
Agile has turned out to be terrible in most organisations I’ve worked at. From officious PMs demanding stupidly mismatched sprints vs the deliverables, to the use of story points as a baseball bat of invented malarkey instead of proper estimation. The useless ceremonies that aren’t tuned to the state of the project. The fantasy land of ill specified tickets and terrible business analysis landing on developers.
Not all of that is purely due to agile but the ephemeral nature of sprints seem to encourage terrible behaviour from the non technical parts of the project management cycle.
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.