You alias rm to do nothing. There is no danger of aliasing rm to echo. The only thing that’ll happen is nothing.

Or are you seriously suggesting that if you do this, you somehow get used to rm doing nothing? Like you’ll just start rm’ing randomly because you know it’ll echo? I mean, stupider things have happened, but… yeah

There are solutions already. Just use them instead of rm

https://wiki.archlinux.org/title/Trash_management

Then can alias rm to echo Use trash instead! or something. You wanna build new habits, not co-opt rm, it could happen easily that you’re ssh’d into a system where your rm alias doesn’t exist or similar

With the difference that code actually is easily changeable, if you need to change a wall you actually need to tear it down, get rid of the waste, likely tear everything down that was supported by it, and completely rebuild it with new materials.

If you need to change the foundations of your code, yes, it’s not always super easy, but it is actually possible and I’ve done it before without super big headaches.

It’s just not comparable.

Because this is not log or debug data as OP said. In any case, what do you think would happen with this data? It will be analyzed by some sort of tool because no one could manually look at this much text data. In text, this can be like 1MB of data per second. So in a normal eye tracking session, probably hundreds of MB. The problem isn’t the storage space, but the time it will take to read that in and analyze it each time, forcing you to wait for processing or use lots of memory while reading it. And anyway, in most languages, it’s actually much easier to store the number values directly (in 8 bytes not the 30something this text representation uses) than to convert them to JSON, all languages have some built-in way to do that. And even if not, sqlite is piss-easy and does everything for you, being as simple as JSON.

There is just no reason to do it like that unless you just don’t think about what you’re doing or have no clue.