Meet the most dangerous feline in tech history.
His name? :(){ :|:& };:
seen from Malaysia
seen from Canada

seen from Malaysia

seen from Malaysia

seen from United States
seen from Maldives

seen from Germany
seen from United States

seen from Malaysia
seen from Maldives

seen from United States
seen from China
seen from China

seen from Germany

seen from United States

seen from Malaysia
seen from United States

seen from United States
seen from United States

seen from Malaysia
Meet the most dangerous feline in tech history.
His name? :(){ :|:& };:
I’ve been working on a comic idea for a while now called Why?2K! and I finally feel comfortable with the direction I’m taking with it to be able to post about it. So here’s some of the main characters! It’s about a bunch of viruses living on a pre 2000′s computer!
we should get a pokemon game that takes place in the far future where youhave to pay for pokemon center. And it isn't free
so a classmate, while trying to make a regular fork bomb, made a forking fork bomb
like, it's a fork bomb, but it starts making fork bombs of its own
all while trying to make a normal fork bomb
Secret Linux Death Number
~$ cat test.c //Secret Linux Death Number long main __attribute__((section(".text"))) = 17936435503883665457L; ~$ gcc test.c ~$ ./a.out
Uh oh...
..as far as I know I'm the first person to stuff this into a single long on 64-bit systems! All the equivalent things I found online took at least 11 bytes.
For those curious, this is an assembly fork bomb. The above C will compile and run fine, and then your computer will become totally unusable (until you restart).
Works on Linux Subsystem on Windows too, crashing Windows.