6 replaced http://askubuntu.com/ with https://askubuntu.com/
source | link

You probably know of that fork bombfork bomb:

 :(){ :|:&};: #WARNING: harmful code

I wonder why it is necessary, for it to parse, to include a space after the opening curly brace.

You probably know of that fork bomb:

 :(){ :|:&};: #WARNING: harmful code

I wonder why it is necessary, for it to parse, to include a space after the opening curly brace.

You probably know of that fork bomb:

 :(){ :|:&};: #WARNING: harmful code

I wonder why it is necessary, for it to parse, to include a space after the opening curly brace.

5 Show appreciation through votes. Thanks not necessary on SO/SX http://meta.stackoverflow.com/a/3021/186664
source | link

You probably know of that fork bomb:

 :(){ :|:&};: #WARNING: harmful code

I wonder why it is necessary, for it to parse, to include a space after the opening curly brace.

You probably know of that fork bomb:

 :(){ :|:&};: #WARNING: harmful code

I wonder why it is necessary, for it to parse, to include a space after the opening curly brace.

You probably know of that fork bomb:

 :(){ :|:&};: #WARNING: harmful code

I wonder why it is necessary, for it to parse, to include a space after the opening curly brace.

4 removed thanks
source | link

You probably know of that fork bomb:

 :(){ :|:&};: #WARNING: harmful code

I wonder why it is necessary, for it to parse, to include a space after the opening curly brace.

Thanks.

You probably know of that fork bomb:

 :(){ :|:&};: #WARNING: harmful code

I wonder why it is necessary, for it to parse, to include a space after the opening curly brace.

Thanks.

You probably know of that fork bomb:

 :(){ :|:&};: #WARNING: harmful code

I wonder why it is necessary, for it to parse, to include a space after the opening curly brace.

3 added actual fork bomb code as suggested
source | link
2 added actual fork bomb code
source | link
1
source | link