@meowski @astheroth

> but only if people foolishly treat it as a black box and use the output without understanding every little thing it did

Yeah, nobody would do that. Nobody would run a curlbash, we haven't had years of actively discouraging understanding code by people that tell you to eval the output of their bullshit $PATH-mangler and then write "2.3 Neckbeard Configuration", which starts with "Skip this section unless you must know what every line in your shell profile is doing."¹ It's not like people have been actively discouraged from reading code or going near confusing, scary things like memory addresses for decades until all we have is 30-year-old JavaScript kiddies with neck tattoos and stuffed animals on their desks that never read a research paper and don't know how to write an interrupt handler. :terrymad:

I fully expect to have to debug their complete horseshit codebases and then in 40 years when, like, twelve guys on earth know how to look at a C program without crying, we'll all captured by FEMA and forced to maintain infrastructure while being fed amphetamines and our brainscans will be fed to the supercomputer that makes all the decisions so that we can be summarily executed for crimes like misgendering some JavaScript++ programmer's² fictive headmates.


¹ Oh, you want to know what I'm running on your machine? Well, if you *must* know: https://github.com/rbenv/rbenv/commit/88e59647aee0abe12cd1cd77d2dce6d33af8caef#diff-b335630551682c19a781afebcf4d07bf978fb1f8ac04c6bf87428ed5106870f5R155 . Ironically, that line was copied without thinking into pyenv's documentation, https://github.com/pyenv/pyenv/blob/master/README.md , shenv's documentation, https://github.com/shenv/shenv/blob/master/README.md#advanced-configuration , jlenv's documentation, https://jlenv.github.io/jlenv/#how-jlenv-hooks-into-your-shell , nodenv's documentation, https://snyk.io/advisor/npm-package/@nodenv/nodenv , phpenv's documentation, https://github.com/phpenv/phpenv/blob/master/README.md#neckbeard-configuration , luaenv's documentation, https://github.com/rcoedo/luaenv/blob/master/README.md#how-luaenv-hooks-into-your-shell , plenv's documentation, https://github.com/tokuhirom/plenv?tab=readme-ov-file#neckbeard-configuration . So it appears that it's optional to even know what every line in your own goddamn README says. SORRY I MEAN README DOT EM DEE. HOW CAN YOU DOCUMENT YOUR PROJECT UNLESS YOU HAVE A SHIT-TON OF BADGES AND SCREENSHOTS AT THE TOP OF THE GODDAMN FILE, THAT SHIT IS ABSOLUTELY MORE CRITICAL THAN EXPLAINING HOW THE NEW HIPSTER-ASS BUILD TOOL IS SUPPOSED TO BE INVOKED OR EVEN WHICH ONE THEY ARE USING.

² JavaScript++ is just a reskin of Scratch only nobody knows how it works and it runs on a machine that emulates an x86-64 that boots into Ubuntu LLLLTS and runs the Docker container that runs the only known copy of JavaScript++.