Live data from Hacker News

PHP Bug #18556 : Setting locale to 'tr_TR' lowercases class names

bugs.php.net

101–110 of 135 posts

Re: PHP Bug #18556 : Setting locale to 'tr_TR' lowercases class names

#101
post #82

Every time an article critical of PHP appears, defenders come out of the woodwork. It's a great language, they say. It's no more flawed than any other language. Critics are just biased. It has problems, but other languages have problems too. People build large apps with PHP, so it must be good. But come on. This language is complete crap. Code spontaneously fails depending on the locale? And the bug has been open for…

> Code spontaneously fails depending on the locale? Code spontaneously hangs when converting 2.2250738585072012e-308? Now count how many languages were affected by that.

How many affected languages left it unfixed for a decade and counting?

Re: PHP Bug #18556 : Setting locale to 'tr_TR' lowercases class names

#102
post #93
post #82

Every time an article critical of PHP appears, defenders come out of the woodwork. It's a great language, they say. It's no more flawed than any other language. Critics are just biased. It has problems, but other languages have problems too. People build large apps with PHP, so it must be good. But come on. This language is complete crap. Code spontaneously fails depending on the locale? And the bug has been open for…

> Code spontaneously fails depending on the locale? It doesn't spontaneously fail. The languages functions are case-insensitive and they documented this. [1] [2] When you change the locale to Turkish the letters change. Thus, the class name changes and no longer works as expected. So it is documented because it may not as expected, but it is not spontaneous. [1] http://www.php.net/manual/en/functions.user-defined.php…

Nowhere in your documentation does it state that a class name cannot be accessed using the exact same, byte-for-byte identical name, depending on locale.

Case sensitivity changing depending on locale would be weird, but at least vaguely sensible. Identical strings no longer matching is just plain wrong.

Re: PHP Bug #18556 : Setting locale to 'tr_TR' lowercases class names

#103
post #94
post #82

Every time an article critical of PHP appears, defenders come out of the woodwork. It's a great language, they say. It's no more flawed than any other language. Critics are just biased. It has problems, but other languages have problems too. People build large apps with PHP, so it must be good. But come on. This language is complete crap. Code spontaneously fails depending on the locale? And the bug has been open for…

Of course, this isn't an article critical of PHP and I'm sure those defenders would just as readily state 'every time PHP appears on Hacker News the PHP-haters come out." While I tend to agree that I would not use PHP for new projects, I would disagree that it's indefensible. All you need to defend it is, "it's easy." In the sense of, "it's nearby, it's within reach." If it happens to be the language installed on you…

The choice to use PHP may be defensible. The PHP ecosystem may be. But I don't believe the language itself is. It's a subtle but important distinction: there are some good reasons to use PHP (although IMO more good reasons not to), but there are few or no good reasons for PHP's problems.

Re: PHP Bug #18556 : Setting locale to 'tr_TR' lowercases class names

#104

Earlier quoted context omitted.

You are the only reasonable voice on the matter I've heard so far. Infinite upvotes from me. We all know PHP has its shortcomings, but there appears to be a witch hunt going on here.

We all know PHP has its shortcomings, but there appears to be a witch hunt going on here. I think some of the witch hunt comes in attempt to steer people away from a language which is badly designed and has a million bugs which cannot be fixed without breaking most of the existing code written for the language. Pestering a language like that is only fair. While I'm sure it gets tiresome for those who for whatever rea…

> ...badly designed...

> ...and has a million bugs...

> ...cannot be fixed...

> Pestering a language like that is only fair.

> ...who has yet to take that dark path

Wow that's a lot of emotive language. Like the man said, witch hunt.

Re: PHP Bug #18556 : Setting locale to 'tr_TR' lowercases class names

#105
post #104

Earlier quoted context omitted.

We all know PHP has its shortcomings, but there appears to be a witch hunt going on here. I think some of the witch hunt comes in attempt to steer people away from a language which is badly designed and has a million bugs which cannot be fixed without breaking most of the existing code written for the language. Pestering a language like that is only fair. While I'm sure it gets tiresome for those who for whatever rea…

> ...badly designed... > ...and has a million bugs... > ...cannot be fixed... > Pestering a language like that is only fair. > ...who has yet to take that dark path Wow that's a lot of emotive language. Like the man said, witch hunt.

While I agree lots of that is emotive, it is hard to argue against the truth in 1. badly designed, 2. bugs, and 3. which cannot be fixed without breaking most PHP code.

The rest follows naturally. Anyway: Have an upvote for objectively dissecting my semi-objective analysis.

Re: PHP Bug #18556 : Setting locale to 'tr_TR' lowercases class names

#106
post #27

Earlier quoted context omitted.

Take the case of software insisting on state input hence unusable outside US. Do you blame the error to George Washington?

Şimdi İstanbul'da oturuyorum. :) (I think that's right, I'm still learning the language...) The comment was meant to be snarky -- obviously, the e-i-ö-ü \ a-ı-o-u rule would be broken, which is the reason for the undotted I. Further, nobody could have anticipated in 1927 the vast extent of automation that we are going through now. For those that don't know Turkish, there is a faced of the language called vowel harmon…

You are missing the point that "new" alphabet was way more before designed than "systems".

Right way should be involving in a process of developing standards, not changing some chars because some new tech come and has problems with the language ( going rampage as you mentioned earlier isn't also a valid solution ).

Re: PHP Bug #18556 : Setting locale to 'tr_TR' lowercases class names

#107
post #104

Earlier quoted context omitted.

> ...badly designed... > ...and has a million bugs... > ...cannot be fixed... > Pestering a language like that is only fair. > ...who has yet to take that dark path Wow that's a lot of emotive language. Like the man said, witch hunt.

While I agree lots of that is emotive, it is hard to argue against the truth in 1. badly designed, 2. bugs, and 3. which cannot be fixed without breaking most PHP code. The rest follows naturally. Anyway: Have an upvote for objectively dissecting my semi-objective analysis.

If someone started again and fixed those issues, would it rock?

Re: PHP Bug #18556 : Setting locale to 'tr_TR' lowercases class names

#108
post #80

Earlier quoted context omitted.

> Nobody seriously criticizing PHP is ridiculing people working with it. I rarely see this. I've found it hard to find a good criticism of PHP that doesn't find a way to insult it's user base. Probably the best criticism of PHP has come from Jeff Atwood's recent post[1] (and even he couldn't go the post without slinging immature, and downright vulgar insults). 1. http://www.codinghorror.com/blog/2012/06/the-php-singu…

That's exactly what I'm talking about, it's insulting and it disappoints me that all of the recent HN threads have been full of similar insults. Their arguments always seem to boil down to "my hammer is better than your hammer, and you're an idiot for choosing the wrong hammer, but luckily I am here to re-educate you".

PHP is so incredibly bad as to have no redeeming qualities to the language whatsoever other than its simplicity in deployment.

Whereas I can have reasoned conversations with proponents of most modern languages, PHP is simply and unequivocally a complete and total failure of a language, and there is resultantly absolutely no room for concession when discussing the language.

PHP is broken and should never be used, and if there are use cases that the alternatives don't address, we should work to address them.

Re: PHP Bug #18556 : Setting locale to 'tr_TR' lowercases class names

#109

Earlier quoted context omitted.

While I agree lots of that is emotive, it is hard to argue against the truth in 1. badly designed, 2. bugs, and 3. which cannot be fixed without breaking most PHP code. The rest follows naturally. Anyway: Have an upvote for objectively dissecting my semi-objective analysis.

If someone started again and fixed those issues, would it rock?

It would be a completely different language.

Re: PHP Bug #18556 : Setting locale to 'tr_TR' lowercases class names

#110
post #36

Earlier quoted context omitted.

> After 5+ years of eloquent, smart programmers* posting long, well researched screeds about what's deeply broken with PHP's design at the most fundamental levels, there is no other conclusion to be reached. Issuing holy decrees from their ivory towers more like. Meanwhile, lots of tremendously successful companies doing real work in PHP each and every day, at the coal face, where it matters. Does their hard work des…

It seems to me that the kicker is the obviously superior alternatives, such as python, ruby, and JavaScript, don't offer the ease of deployment that php has via mod_php, and instead insist on the developer writing a web server. While there are advantages (performance, control) to the web server approach it is clear that there are advantages (simplicty) to being able to stick code snippets in web pages. If you could d…

You are wrong to say that these 'insist on the developer writing a web server.' All you have to do is choose a web server, which was also true with PHP (even if all you want to do is choose Apache).

Some of these servers are so easy to install and use, so much EASIER than Apache, that it really gets ridiculous to complain about.

mod_python has been deprecated for years in favor of mod_wsgi, which uses an actual standard. That you don't know this shows that the problem is too much documentation guiding people to things which are no longer modern or standard. If you use Apache, use mod_wsgi, it is infinitely better.

webfaction costs $5.50/mo, lets you do proper Python deploys rather than endless hacks and has good support, if you need cheap Python hosting.

Post reply on HN