PHP Working On A "Next Generation" Branch

[phoronix]

Phoronix: PHP Working On A "Next Generation" Branch

PHP developers have shared they are currently developing phpng, a next-generation branch of the code working towards JIT compilation...

http://www.phoronix.com/vr.php?view=MTcwMzI

[spirit]

Phoronix: PHP Working On A "Next Generation" Branch

PHP developers have shared they are currently developing phpng, a next-generation branch of the code working towards JIT compilation...

http://www.phoronix.com/vr.php?view=MTcwMzI

Why reinvent the wheel ?

facebook have already done a lot of work with http://hhvm.com/

[droidhacker]

Why reinvent the wheel ?

facebook have already done a lot of work with http://hhvm.com/

Because their wheel is triangle shaped.

[werfu]

Because their wheel is triangle shaped.

A really fast one though. I do think that HHVM could have the potential of replacing PHP altogether if the PHP people decided to drop some legacy PHP stuff HHVM don't support. Sure some rough angles would remain, but HHVM is already where this PHP NG is heading.

[Daktyl198]

JIT is awesome and all, but it doesn't stop PHP from being a bad language.

Don't get me wrong, I USE it and I LIKE using it, but they could introduce some breakage in version 6 to steer it towards a better direction... (drop a bunch of legacy stuff, rename poorly named functions, etc)
Function naming:

http://phpsadness.com/sad/4

http://phpsadness.com/sad/48

http://phpsadness.com/sad/15

Just as examples.

[psychoticmeow]

JIT is awesome and all, but it doesn't stop PHP from being a bad language.

Don't get me wrong, I USE it and I LIKE using it, but they could introduce some breakage in version 6 to steer it towards a better direction... (drop a bunch of legacy stuff, rename poorly named functions, etc)
Function naming:

http://phpsadness.com/sad/4

http://phpsadness.com/sad/48

http://phpsadness.com/sad/15

Just as examples.

It's changed a lot, but function naming probably wont be fixed until/if they implement methods on primitive types, this would give them the perfect opportunity to sort out the majority of the issues.

You should also read this article, or at least the last section about upcoming changes to PHP: http://nbsp.io/you-cant-tell-me-php-hasnt-changed/

[Jonjolt]

It's changed a lot, but function naming probably wont be fixed until/if they implement methods on primitive types, this would give them the perfect opportunity to sort out the majority of the issues.

You should also read this article, or at least the last section about upcoming changes to PHP: http://nbsp.io/you-cant-tell-me-php-hasnt-changed/

I don't want to nit pick but if there are methods on primitives.. they wouldn't be primitives in the first place?

[Daktyl198]

It's changed a lot, but function naming probably wont be fixed until/if they implement methods on primitive types, this would give them the perfect opportunity to sort out the majority of the issues.

You should also read this article, or at least the last section about upcoming changes to PHP: http://nbsp.io/you-cant-tell-me-php-hasnt-changed/

The first link:
That all looks very interesting (it might give me a reason to finally start using the OO interface more than when is absolutely necessary ), but I don't really agree with his comment of "The vast majority of math functions don?t do well as methods either."... I feel like if you're going to introduce a new Method-based API for two variable types, you should include it on any others that may benefit from it. Stringing together math functions can be just as messy as string functions (that he criticized earlier in the article), so this new API could definitely help with that...

Link two:
That's just awesome... not much to say there