[kalleboo]

If this is such a dealbreaker for developers in Turkey, why have none of them, in the 10 years this bug has been alive, submitted a patch for it? PHP is open source, it relies on code submissions.

edit: not trolling, just curious. What drives people to complain about specific, well-defined open source bugs without any effort to fix it? I understand hard-to-nail down issues like user experience, but this shouldn't be that hard to plan out and fix independently.

[slurgfest]

If there are viable alternative projects which never had that problem, you can save all the time rather than trying to salvage someone else's broken software. It's a lot less time and trouble. What reason do I even have for fixing your project? I don't owe PHP loyalty when it is broken for me.

If there are viable alternative projects which are more responsive to bug reports, that is more promising for the future - if a second bug I see is reasonably likely to be fixed in the future, I can feel more confident basing my own code on it.

People spend months and years writing apps on top of things like PHP and once they have the code they don't necessarily have a lot of choice. At that point maybe you fix the bugs in your dependencies rather than rewrite your own app. But when you have a choice, you don't adopt a tool which is going to leave you with this much technical liability.

This is offered peacefully in an attempt to explain the question which seems to confuse you.

[josteink]

See Mithrandir's comment: http://news.ycombinator.com/item?id=4187943