Mkdir foo && cd foo

mkdir foo && cd foo
echo > -i
echo > yourself
rm *
Outputs:
remove yourself?
Don't tell me why this happens, everyone knows, but this is bullshit. Why are UNIX and/or UNIX-like systems so shit?

Attached: 1546919243508.jpg (800x406, 77K)

Other urls found in this thread:

youtube.com/watch?v=L9v4Mg8wi4U
web.mit.edu/~simsong/www/ugh.pdf
twitter.com/NSFWRedditVideo

Attached: 636sandwich01.png (465x387, 38K)

Excuse me

Its a hidden joke

Because the standard is optimized for a faster PDP-11

Unix is still here because the thing that would surpass Unix would have to come out of some environment which would need to surpass the environment where Unix was created.

The major tech innovation today is in evil ad-tech companies and not some hippie laissez-faire kind of moonshot enginnering org like AT&T or PARC.

You mean Bell Labs?

1

The problem is that UNIX can't advance either, because of POSIX

Yea, posix could be obsolete. If you hear BSD folks envying Linux innovation, and install base, one wonders if posix needs to be a thing, still.

Can you elaborate on this

because you don't know how to use them
rm -- *
here you go

not op, but posix was the vehicle to get the dozens of unix variants under the umbrella in the 80s and 90s. But most of them died, Solaris, AIX, HP-UX, mostly gone.

IRIX, rip

Attached: jurassic-park.jpg (980x490, 98K)

Shit as well

remove yourself

Replacing the Unix tradition
youtube.com/watch?v=L9v4Mg8wi4U

web.mit.edu/~simsong/www/ugh.pdf

Attached: uhh-cover.gif (400x508, 191K)

I mean fundamentally this is happening because the shell doesn't have any sort of type system. Everything is text, so rm doesn't know how to differentiate between arguments and filenames. I think Powershell had a good idea in adding a type system to a shell, but they fucked it up by making all of the functions horribly verbose and making it Windows only.

rm ./*
there you go

>he thinks AIX is gone

Oh, honey...

try this in a VM:
echo > -rf
echo > \~
rm *

>be me
>read this
>oh how bad could that be?
>try it
>wtf, rm * == rm -i yourself ????
>let it run
>-i is still present
>it lingers like a fucking plague
>rm [tab]
>rm -i
>rm -i -i -i -i -i -i -i -i -i -i -i...
>oh god...
this was a mistake, how do we delet?

>echo "`rm *`"
good thing no sudo or i would have lost the whole system.

so what you're saying is we need to write a modern interpreted shell scripting language which has implicit non-declarable types?
Any other ideas besides that, i might actually try it.

Unix was a shitty and proprietary system in the 70s and OP is a faggot who can't into. /

>they fucked it up by making all of the functions horribly verbose
as a result of making it object-oriented.
If we're having a discussion about how we can improve the Unix design model or replace parts of it, one thing is clear.
The shell language can NOT be object-oriented.

rm ./-i