1. [:39149172] <skipped>
2. [:39149168] <processed without return value>
3. [:39149163] <skipped>
4. [:39149157] <processed without return value>
5. [:39149141] <skipped>
6. [:39149138] <processed without return value>
7. [:39148947] <skipped>
8. [:39148940] <processed without return value>
9. [:39148892] <skipped>
10. [:39148890] <processed without return value>
11. [:39148883] <skipped>
12. [:39148880] <processed without return value>
13. [:39148834] <skipped>
14. [:39148832] <processed without return value>

stackoverflow: 528
math: 501
superuser: 148
codegolf: 122
physics: 81
serverfault: 73
askubuntu: 64
apple: 58
unix: 51
english: 48
travel: 42
gaming: 40
electronics: 37
android: 37
workplace: 34
es.stackoverflow: 30
webapps: 29
wordpress: 28
scifi: 26
security: 26
dba: 25
mathematica: 24
stats: 24
money: 24
salesforce: 23
rpg: 23
worldbuilding: 22
drupal: 21
arduino: 20
sharepoint: 20
gis: 19
mathoverflow.net: 18
bitcoin: 17
diy: 17
gamedev: 17
meta: 17
graphicdesign: 16
ell: 14
softwareengineering: 13

>
> THIS FORK BOMB ALWAYS REMINDS ME OF THE SOMETHING AN AI PROGRAMMING TEACHER SAID ON ONE OF THE FIRST LESSONS I ATTENDED "TO UNDERSTAND RECURSION, FIRST YOU MUST UNDERSTAND RECURSION". AT IT'S CORE, THIS BOMB IS A RECURSIVE FUNCTION. IN ESSENCE, YOU CREATE A FUNCTION, WHICH CALLS ITSELF, WHICH CALLS ITSELF, WHICH CALLS ITSELF.... UNTIL SYSTEM RESOURCES ARE CONSUMED. IN THIS SPECIFIC INSTANCE, THE RECURSION IS AMPLIFIED BY THE USE OF PIPING THE FUNCTION TO ITSELF AND BACKGROUNDING IT. I'VE SEEN THIS ANSWERED OVER ON STACKOVERFLOW, AND I THINK THE EXAMPLE GIVEN THERE ILLUSTRATES IT BEST, J…