Can we please talk about how UN*X shell is still not fixed in 2018?

What's the analogy even mean? Making it so that mv, cp and rm don't assume your data is easily replaced is nowhere near adding some terrible user burden. Nor is fixing retarded bugs.

when confronted with logical refutations these people just sperg out with false analogies instead of ever conceding defeat.

THIS is why you need a "path" data type, separate from the "flag" data type.

Why the fuck am I typing RM then

inb4 *rm

What the fuck do you even want? If you want your hand held through basic file operations then use a desktop's UI. If you want to do low level operations that are often unsafe use a shell.

Can't you just use quotes?

Unix filenames are pretty bad, in some cases they're even executable. The alternative is breaking compatibility and convenience though so just be less shit. A single find command can fix all your bullshit filenames on your whole system at once.

I know right OP?
If only they were using a binary format with well defined boundaries, like a null characters. But maybe systemd could be managing a shell too, that will fix the problem!

Attached: extremely painful.png (226x261, 73.69K)