3 ms·
i see how using the forward slash could have presented problems, but it doesn't seem to be a problem for other languages, so... i guess part of what really str
by readonthegoapp 5y ago
i see how using the forward slash could have presented problems, but it doesn't seem to be a problem for other languages, so...
i guess part of what really strikes me about it is...it's a _back_slash.
like...something Bill Gates would approve of.
backslashes are not open source-y or unix-y or linux-y.
the 'history of php' shows this snippet:
<!--include /text/header.html-->
which, to me, just indicates that PHP has been comfortable with forward slashes in all sorts of contexts for a long time, it was built to resemble-ish C, etc. etc.
i thought one of the folks making the decision might have been like:
Backslash? Nah.
Everyone has their hangups -- right now, mine is:
OK, I'm gonna use Laravel. I'm gonna use the starter kits, they're free, PHP is doing fine, much better than Python actually/probably, it's prob 1,000x faster than Python, Python still doesn't know what version it wants to be and will prob never get to another version anyways, but... can I really look at those PHP backslashes?? No. No, I can't. I'm using python/django instead. ... We'll see.
I've been thinking about this for months. I figure in a few more months I'll figure out how to disqualify python/django.