Re:PHP Must Die
by csomar on Saturday January 09, 2010 @07:07PM
(#1042248)
I think "PHP Must Die" is a lot exaggerated, I think "PHP should be improved" is a better title!
[ Parent
| on HN ]
The problem is most of the broken behavior in PHP is never going to be fixed because it would break compatibility.
Printing a warning would be easy enough, you could disable the warning if you want it to work like this. Leave that for one generation with a 'deprecated' attached to it, remove in the major release after that.
Lots of things that were wrong have been changed like that.
The biggest one remaining of the 'old' bugs which I think really would break too much is the strpos return value in case of no match (which is 'false' but 0 is a legal return value as well, -1 would have been a far better choice).
The improved version of PHP is Perl. Which has been around longer than PHP...
Re:PHP Must Die
by potatolicious on Saturday January 09, 2010 @08:28PM
(#1042403)
I write Perl daily - and sometimes I'd rather deal with PHP...
You're doing it wrong.
Re:PHP Must Die
by ThinkWriteMute on Saturday January 09, 2010 @07:19PM
(#1042278)
Yes, but so much would have to be improved that starting off with a clean slate might be easier, yes?
Re:PHP Must Die
by ryanwaggoner on Saturday January 09, 2010 @07:45PM
(#1042329)
What does "the slate" mean here? There's not one master language out there, so "killing PHP" means one of two things:
1. Using something else for an individual project (maybe a good idea) 2. Replacing all PHP with something else (impossible)
Since a massive amount of the web runs on PHP, "starting off with a clean slate" would definitely NOT be easier. In fact, it would be impossible.