Re:Including “And. And. And. And. And.” in a Google doc caus...
by omnicognate on Friday May 06, 2022 @06:29AM
(#31283534)
As another commenter said it was "one of many things". Also, it's not the fact that it was non-English that was off-putting. It's more the fact that the T_ identifier was used, presumably via a macro.
People are often defensive about PHP, but at the end of the day we choose our tools. I wrote a significant amount of PHP for a brief period and out of maybe 20 or so languages I've used professionally I found it by a wide margin the least pleasant to work with. Supposedly it has improved a lot, and I'm glad if so. But I have no desire to use it again, and am unlikely to ever have a reason to.
Re:Including “And. And. And. And. And.” in a Google doc caus...
by josefx on Friday May 06, 2022 @01:09PM
(#31287540)
Also the only information available to the developer when it was added in PHP 3 in 1997, good luck Googling that error. They didn't add the actual token to the error message until PHP 5.4 over a decade later.
One can like or dislike PHP for a variety of reasons, but surely being put off it for life because a non-English string is exposed to the end user is a bit much.