Rasmus Lerdorf's analysis of XHP

http://toys.lerdorf.com/archives/54-A-quick-look-at-XHP.html

by mattwdelong • 16 years ago

72 20 16 years ago

toys.lerdorf.com

Heh, now I see why they had to invent HipHop. It's an interesting idea - trade off speed for readability and security, and then write a PHP->C++ compiler to recover the speed you've lost. I wonder whether it would've been easier to use a language + templating system that gets security right in the first place, though.

ashu• 16 years ago

XHP development started very very recently and had absolutely nothing to do with HipHop.

robryan• 16 years ago

From those benchmarks though it seems it would only be really effective with HipHop in a high CPU usage environment.

paul3• 16 years ago

He's benchmarking based off of a 10 line PHP program and then extrapolating that this is why HPHP is needed?

codexon2• 16 years ago

It's a joke.

HPHP's 50% speed boost does not make up for a templating engine that 43 times slower.

paul3• 16 years ago

No, it's stupid because a 10 line program isn't the least bit representative.

rbanffy3• 16 years ago

His benchmark is all about the template engine because that's what XHP changes.

The impact of XHP and HPHP depend very much on what you are doing to serve your requests.

_3ex7• 16 years ago

The title of the actual page is called "A quick look at XHP"

wesley• 16 years ago

I see no reason those XHP templates couldn't just be cached as regular old PHP. It's a nice tool to have during development only.

rbanffy3• 16 years ago

Call me old-fashioned, but I have been weary of source-code transformations since I first touched C++

flogic• 16 years ago

Unless you code in raw machine code, everything is a source code transformation.

encoderer• 16 years ago

APC is doing that, just one step better, by caching them as PHP Opcodes.

prodigal_erik• 16 years ago

  return $this->renderBaseAttrs() . ' />';

No wonder it's expensive. If you serialize a tree of objects by concatenating subtrees into substrings, most values are copied many times depending on the depth of the tree, and you end up doing O(n log n) work. But as for the alternative

  there was basic XSS filtering in place for the naked
  $_POST['name'] variable in the plain PHP version

isn't knowing you have to encode some but not all of your output worse than just encoding all of it? This is the kind of design mistake that leads to databases accidentally full of HTML entities. Or more likely, half full.

Daishiman• 16 years ago

Well you know what they say about putting lipstick on a pig...

Rasmus Lerdorf's analysis of XHP

Related Stories