dvqc

You have processes more formal and thorough than their code implementation? Really?

At the end of the day, is it the cover-every-possible-bitflip-and-gamma-ray-bursts process that produces results out of thin air, or is it the machine running the code?

I don't believe this is arguing in good faith.

Because the code is the entirety of the process. Any graph can be wrong, but the code cannot, because it is the implementation. The purpose of a graph is to allow the visualization of the process in an understandable manner. If it doesn't abstract away much from the code, you might as well look at the code directly

A trottinette is actually called a scooter in english. I believe a "motor scooter" is what we in France call a scooter.

Having an "e" pronounced "a" in french is very rare, I would also intuitively only expect it to happen when the "e" is followed by two consonants. A french person would likely mispronounce scheme either as "shem" or "skem", based on their familiarity with english. We have "Schéma" for "schematics", and we pronounce it "shem-a"

I believe what you're looking for is Jq for the json prettifying/manipulation, and nushell for tabular text (not sure about that one, I've only seen it mentioned occasionally). I strongly believe this should not become the job of the terminal, as it makes it all the more complicated and would possibly deter people from writing the kind of specialized, portable tools that are Jq and nushell for instance. At most, I think it should be a job for an ncurses application