PHP tends to be at the bottom of the "language quality totem pole" because as a language it's pretty low quality. The PHP interpreter may be fine as a piece of software, but that's a completely separate matter from being a quality language.
PHP tends to be at the bottom of the "language quality totem pole" because as a language it's pretty low quality. The PHP interpreter may be fine as a piece of software, but that's a completely separate matter from being a quality language.
> PHP tends to be at the bottom of the "language quality totem pole" because as a language it's pretty low quality. The PHP interpreter may be fine as a piece of software, but that's a completely separate matter from being a quality language.
It is specifically for that reason that I broke it down in to two parts, and apparently we agree on the language quality from a design point of view, but from a 'have to use this in production' point of view we do not.
> You say the PHP devs have a sharper focus on quality than other languages;
That's a straw-man, I said no such thing, but it does happen to be my experience that the PHP devs respond very quickly compared to other platforms / languages.
> Can you provide and kind of evidence for those claims?
And no, I'm not going to provide you with any 'evidence' for my claims, you can take my word for it. This is not a court of law, and besides that I never made any claims about other languages before this comment and I don't feel like putting other languages and/or their developers down.
I know PHP as a language has its flaws and that there are some unfortunate choices made in the past that are very hard to undo but that's no reason for losing all objectivity.
It's great that the PHP devs do that! Is that a compelling reason to use the language? I'm not so sure.
>That's a straw-man, I said no such thing;
You said:
> The team that makes PHP makes quality a higher priority than just about any other language
Can you explain to me what I misinterpreted?
> And no, I'm not going to provide you with any 'evidence' for my claims, you can take my word for it. This is not a court of law, and besides that I never made any claims about other languages before this comment and I don't feel like putting other languages and/or their developers down.
It's a little silly to make a comparative statement like "The team that makes PHP makes quality a higher priority than just about any other language" and then refuse to provide examples of where this happens and matters. If you'd just said "The PHP devs respond quickly to bug reports", sure, but when you start saying "They do this better than other languages", you're implicitly already "put other languages and/or their developers down". In a case like that, I don't think it's out of line to ask for examples; if there are major failings in other languages that go ignored and unaddressed, then that's certainly worth some attention. If there aren't, the whole point is moot anyhow. If there are examples of systemic problems that go ignored in other languages, I'd like to know about them - that may matter when I choose a language for a project.
I'm not interested in trashing PHP here; I use it on a daily basis, and get a lot done with it. I also use Ruby, Python, Javascript (both server and clientside), bash, and the occassional perl on a daily basis, and don't have problems with mysterious segfaults and unexplained crashes from 2-year-old bugs that would somehow make PHP's lack of such problems a major marketing bulletpoint. I don't understand your position at all, because as far as I can tell, it's "The PHP interpreter is mostly bug-free, and bugs get fixed quickly" (which is great!), but...what language with showstopper bugs survives mainstream use?
>> The team that makes PHP makes quality a higher priority than just about any other language
> Can you explain to me what I misinterpreted?
Yes, that that was terra_t, not me making that claim.
For example, in ASP.NET, I've had a whole team of developers swear up and down that there are no static variables in a particular segment of code that could be the subject of a race condition. Sure enough, I go in there and find one that's hidden away in a very obscure location.
Java has the same problem, as does any environment that exposes threads to the language. Sure, in theory you could do some very nice things by sharing data structures between requests, but practically the whole programming style of PHP encourages people to avoid horrible horrible problems with concurrency, and there are no language features, even in the laboratory that practically make those problems go away.
To take another example, the urldecode function in CPAN has been wrong for 15 years. If you want to write a urldecode that works right, you've got to write your own (possibly using the built-in for a base). Similarly, the URI object in .NET sometimes does incorrect transformations on URIs, and you need to use string URIs if you want to make interoperable semweb systems... PHP has the lowest fraction of 'things that say they work but really don't work' of any web programming languages, and that's the reason why it is so successful. Other languages are "blub" because they don't recognize that it's even possible for things to be this easy.