This is my favorite. I did php early in my career and for years I would have to Google “<lang> equivalent explode/implode” because it was so memorable
Filthy barbaric PHP developers. It’s
Split()andJoin().
I loved explode back when I frequently used PHP
Linux: kill
Also Linux: zombies, orphans
Daemons
Crypt
Meanwhile docker compose: --remove-orphans
Don’t forget
fork!Just make sure you don’t panic()
I love die()! but PHP has exit(), too, and it does the same thing
C++ is actually std::exit(), exit() is C.
Friends explained that to me, yeah. Oh well
MS Developers: Kill all children
Well I didn’t wake up today expecting to watch a video about task manager, but here I am.
Now watching the Pinball video before going to bed.
php, the Dark Souls of the programming languages
Because?
Y O U D I E D
I heard the sound when I read this
I have never used
System.exit()orsys.exit(). What is a use case where you would call these explicitly?For example if you want to set an explicit exit code. Calling python scripts will usually result in an exit code
0after the script is run. If you want to set a different exit code for example1to indicate some error occured you can do that viasys.exit(1).Same thing applies to other languages of course.
exit()-ing your step-sys already seems pretty explicit…
Applications where you aren’t using some sort of framework. Usually MVC or other frameworks would handle this or are designed to continuously run.
Perl is funnier, as these are valid ways of exiting with an exception:
readFile() or die;
die unless $a > $b;
Libdbus: Trying to remove a child that doesn’t believe we’re it’s parent.
PHP is so bad even PHP wants to
die().Fun fact: there’s a shorter way to throw a NullPointerException:
throw null;Because
throwthrows a NPE if the parameter is null
