Live data from Hacker News

The future of PHP, at a distance

pooteeweet.org

11–20 of 50 posts

Re: The future of PHP, at a distance

#11
post #8

Kinda wish they would drop backwards compatibility once in a while. I get why they don't but that's why PHP is just the most popular mediocre language. There should be scheduled non backwards compatible releases for every language (say every 10 years) that's the only way they can improve and not just get replaced when better ones come along.

PHP deprecates features all the time... you're an idiot.

Re: The future of PHP, at a distance

#12
post #9
post #8

Kinda wish they would drop backwards compatibility once in a while. I get why they don't but that's why PHP is just the most popular mediocre language. There should be scheduled non backwards compatible releases for every language (say every 10 years) that's the only way they can improve and not just get replaced when better ones come along.

Python did that, and now everyone loves to hate it.

I like Python3. They fixed all the inconsistencies in the language.

Sucks that some people are still stuck with 2.7 but it's definitely worth upgrading if you can.

Re: The future of PHP, at a distance

#13
"Also what about windows users, still a very significant portion of the PHP user base?"

Yes, especially during development. I am toying w/ a PHP implementation on top of luajit, written in PHP so it may be more hackable and bootstrapped.

The real problem is PHP fails to define a specification that implementations can follow (though they probably weren't prepared for the current situation). Sadly the runtime becomes the spec, and with such a large standard library, it's hard to predict what happens in dynamic languages when you send in something undocumented. In order to work w/ the myriad of PHP projects out there, unfortunately you have to mimic the undefined aspects.

We are headed towards a more fragmented PHP than we already have. I've had enough problems changing PHP versions (regressions and undefined standard function changes), now with HHVM, you will have one more fragmentation piece. I'm all for different implementations. The saving grace I've found is all the language phpt files (but doesn't help w/ parsing and many compile-time errors).

Re: The future of PHP, at a distance

#14
post #8

Kinda wish they would drop backwards compatibility once in a while. I get why they don't but that's why PHP is just the most popular mediocre language. There should be scheduled non backwards compatible releases for every language (say every 10 years) that's the only way they can improve and not just get replaced when better ones come along.

PHP deprecates features all the time... you're an idiot.

Not the same thing. PHP needs a total makeover not some minor tweaks.

And you're very rude please go away.

Re: The future of PHP, at a distance

#15
post #8

Kinda wish they would drop backwards compatibility once in a while. I get why they don't but that's why PHP is just the most popular mediocre language. There should be scheduled non backwards compatible releases for every language (say every 10 years) that's the only way they can improve and not just get replaced when better ones come along.

PHP4 vs PHP5 - There was a lot of breakage at the time and was quite painful for many.

Re: The future of PHP, at a distance

#16

google app engine now supports PHP and they completely reimplemented the language. it is extremely fast and seems to already do all the things this story eludes might happen.... they already have.

They did not completely reimplement the language, it appears to be the standard implementation. Compare https://github.com/GoogleCloudPlatform/appengine-php/tree/ma... to https://github.com/php/php-src

Re: The future of PHP, at a distance

#18

From my understanding, if the day ever comes where the official PHP engine is switched to HHVM, it would catapult performance past Python and Ruby in pretty much all scenarios.

Versus native Python and Ruby, perhaps. Versus PyPy and Ruby Motion? Probably not.

Re: The future of PHP, at a distance

#19
post #14

Earlier quoted context omitted.

PHP deprecates features all the time... you're an idiot.

Not the same thing. PHP needs a total makeover not some minor tweaks. And you're very rude please go away.

It's like how forest fires are a bad thing, but not having forest fires for a long time is even worse since the amount of underbrush just grows to the point where a massive calamity is unavoidable.

Backwards compatibility is a noble goal, but it should be done by add-ons, not core features.

Apple constantly throws out features to keep the core product leaner. Is this annoying and disruptive to the end users? Yes. It just means that new adopters, which is their constant goal, do not have to deal with this legacy.

X11 support was dropped, but you can still get it through third-party XQuartz. PowerPC code doesn't run out of the box, but there are emulators that work just fine.

PHP should show a little more confidence in itself.

Re: The future of PHP, at a distance

#20
post #8

Kinda wish they would drop backwards compatibility once in a while. I get why they don't but that's why PHP is just the most popular mediocre language. There should be scheduled non backwards compatible releases for every language (say every 10 years) that's the only way they can improve and not just get replaced when better ones come along.

Chances are good that there will be a PHP 6 release in the near future (~3 years?) that contains a non-trivial amount of BC breakage. At least the idea has gained some momentum recently. But no branch / timeline yet ;)
Post reply on HN