in reply to Perl style: Arguing against three-argument join()

Go for the simple. Make the programmer's intent clear and obvious. Also consider future changes to the code:   try to make the code as maintainable as possible. (After you get smooshed by that bread-truck, no one's gonna want to “dig you up so you can fix it.”)

“At 2.4 gazillion ops per second, nobody can hear you scream.”