Live data from Hacker News

HipHop VM: now at 98.5% PHP framework parity, 16% faster

hhvm.com

61–70 of 112 posts

Re: HipHop VM: now at 98.5% PHP framework parity, 16% faster

#61
post #57

Earlier quoted context omitted.

wow, you really hate PHP. That that mold infested roof caved in house runs a great deal of the web.

I'm actually a tad worried about what will happen to all the people who coded primarily PHP for their whole life when that roof finally collapses. Seems like it might look a bit like what happened with Symbian / Nokia -- they also had a massive cognitive dissonance over the quality of the developer environment, and when the system finally broke, it broke quickly and in a nasty way. Then again, it's not impossible to…

I'm curious how you came to the conclusion that something that occupies, by conservative counts, over 75% of the web as being "a blatant fallacy".

Symbian / Nokia went the way of the dodo because the end user fell in love with the ease of use of the iPhone.

In our case, the end users are people who use the internet, not the ones writing code.

Your argument is about as ridiculous as I can imagine, with no real data to back it up other than your frothing hatred of a language.

Re: HipHop VM: now at 98.5% PHP framework parity, 16% faster

#62
post #58

Earlier quoted context omitted.

It _is_ their fault, for repeating the stupid mistakes that Kernighan, Ritchie, et al made when designing Unix and C.

Short names weren't really a mistake when K&R made them.

Yes, for some time (the dark ages I like to think) programmers had to sacrifice productivity to make things faster, or to make them fit in memory. The original C compiler had a 6 character limit on variable names, leading to abominations like `strstr()`.

Fortunately, by the Pentium era, which was when PHP was designed, those times were long gone.

"X made this design decision before us" is never a good justification for any design decision unless the decision is truly arbitrary (i.e., are arrays 0 or 1 indexed?) -- then it might be better to stick to what's more familiar. If it was a good design decision then, then there must have been some reason at the time that should be true now to give a good case for repeating a design decision.

Re: HipHop VM: now at 98.5% PHP framework parity, 16% faster

#64

I wonder how hard it would be (for me) to take php and change all function names to be consistent. All PascalCase and spelled out (no awful abbreviations). Then download the documentation and change it there as well.

First you'd have to make sure your string hash function isn't strlen.

I thought this was a joke at first....

Re: HipHop VM: now at 98.5% PHP framework parity, 16% faster

#65
post #17

I see a lot of familiar frameworks and CMSs except one. Wordpress. Any idea why Drupal and Joomla would be listed without WordPress?

I haven't looked into integrating with the test harness, but the test suite was pretty easy to get running locally. Unfortunately it crashes halfway through, but up until that point, the majority of the tests passed.

Re: HipHop VM: now at 98.5% PHP framework parity, 16% faster

#66
post #58

Earlier quoted context omitted.

It _is_ their fault, for repeating the stupid mistakes that Kernighan, Ritchie, et al made when designing Unix and C.

Short names weren't really a mistake when K&R made them.

I find the juxtaposition between PHP's short function names taken from C, and things like T_PAAMAYIM_NEKUDOTAYIM to be rather funny.

Re: HipHop VM: now at 98.5% PHP framework parity, 16% faster

#67
post #28
post #17

I see a lot of familiar frameworks and CMSs except one. Wordpress. Any idea why Drupal and Joomla would be listed without WordPress?

Wordpress' unit test suite was just too gnarly to get running with our test harness. Send us a pull request if you can get it working. https://github.com/facebook/hhvm/blob/master/hphp/test/frame...

It seems at the moment there's no way to have a DB server available when running tests. Is that correct? Until that happens, I don't imagine WP tests will be able to run.

Re: HipHop VM: now at 98.5% PHP framework parity, 16% faster

#68
post #31

Earlier quoted context omitted.

Ahh yes, take the most criticized aspect of Java -- the obscene verbosity -- and cram it into PHP. Sounds wonderful.

I'll take a long function name over an incomprehensible one any day.

Expanding abbreviations doesn't improve clarity.

E.g. XMLHttpRequest vs ExtensibleMarkupLanguageHypertextTransferProtocolRequest

and ftp_ssl_connect vs FileTransferProtocol_SecureSocketLayer_Connect

or if you want to get really ridiculous:

MysqlndUhConnection::sslSet becomes MyStructuredQueryLanguageNativeDriverUserHandlerConnection::SecureSocketLayerSet

Re: HipHop VM: now at 98.5% PHP framework parity, 16% faster

#69
post #31

Earlier quoted context omitted.

Ahh yes, take the most criticized aspect of Java -- the obscene verbosity -- and cram it into PHP. Sounds wonderful.

I'll take a long function name over an incomprehensible one any day.

While you're at it why don't you fix: (needle, haystack), (haystack, needle)? :P

Re: HipHop VM: now at 98.5% PHP framework parity, 16% faster

#70

Earlier quoted context omitted.

I'll take a long function name over an incomprehensible one any day.

While you're at it why don't you fix: (needle, haystack), (haystack, needle)? :P

With array functions, the needle is first. With string functions, the haystack is first.

https://gist.github.com/salathe/1672543

Post reply on HN