I know they can be considered bad practice, but in practice you use at at least a couple of them at least once in every project! And you use it because the alternative would be even uglier. (Also, what's the point in having a language with a separate namespace for functions and variables - Perl and Common Lisp being the only other ones I know of - if you can't at least have fun with variable variables and using a string directly as a function :) )
...also, they've "downgraded" PHP's closures mechanism. I mean, with:
return function foo($a, $b) use ($outer1, $outer2) { ... }
...PHP managed to do things better then all other dynamic languages - finally a way of being explicit about what variables from the outer scope you drag into a closure! The Hack guys totally missed the point - they've made everything stricter, but they relaxed this constraint and reverted one of the few good ideas in PHP.
Their VM may be awesome, but their language is horrid - they take away the "fun" features of PHP but don't fix any of the bad language design issues. It's like throwing away the baby and keeping the bath water - yeah, the water will keep you alive for a few more days in the desset, but the baby can actually be fun to play with.
==> jokes aside, they are pulling in a very different direction from the one of the core PHP devs... this alone makes me expect less from the entire PHP system as a whole. They just made the PHP equivalent of Perl 6 vs Perl 5. But at least they are using their "Perl 6" and it works fine for them.
If we could at least start to see shared hosts offering support for Hack and XHP it would seem more hopeful. (btw, you think PHP devs would like this? I was kinda pondering over it as a business idea...)
> they are pulling in a very different direction from the one of the core PHP devs
when a sole company creates its own modified "version" of an existing language, and that company has a stated motto of "move fast and break things" why would you possibly trust them to maintain any features/compatibility longer than they themselves see a use for it?
To know that the returned function can keep state? And if it does, to easily scan for side-effects via modified state? And to do this without carefully reading the entire body of the closure? It's a little bit like a "poor man's replacement for what a monad can be useful at" or `[Pure]` in C#. True, not much use in code you have written, but great for working with and even refactoring other people's code that you don't fully understand.
...to be honest, it's the kind of feature that I'd like to see in Javascript, not in PHP, to help me easily scan through callback hells in other people's code. It's true that callbacks don't tend to be abused in PHP and we don't have event labyrinths and long running event driven apps that can grow in memory usage, but these things will crop up, and when they do we'll have one less tool to make code more explicit and easier to read.
I guess the fate of all good ideas that land in PHP is to be ignored, hated and then forgotten :)
Many engineers here use vim and emacs. We ship integration scripts for both of them -- in `/usr/share/hhvm/hack` in the Debian and Ubuntu binaries, in `hphp/hack/editor-plugins` in the github repo.
So coincidentally I work at Facebook and know a bunch of these guys pretty well, but I don't actually interact with the Hack stuff at all (as I work in infrastructure doing flash and network stuff, primarily). I recently played around with the Open Source hack stuff and I installed it on my VPS.
Has anyone else played with Hack in a productionish environment? I'm just wondering what deployments and stuff are actually looking like in the world outside of Facebook.
Considering that you can convert PHP files to Hack by just changing the opening tag, I think it would be very similar to the way HHVM is used currently.
Oh I see. I think the best answer to your question is the Hack example site https://github.com/hhvm/hack-example-site. It contains the source for the Hack site along with build instructions.
Although it's not an MVC site, they do a lot of inline HTML ...
Yeah, almost everyone in the real world is using it via FastCGI. People have a huge investment in the configuration and operation of their existing http server (nginx or apache).
I work at Facebook as well, but mainly in JavaScript so I haven't done a lot of PHP either :)
You could use a common PHP framework like FuelPHP, Laravel or Kohana. I'm not sure which frameworks are 100% compatible with HHVM, but I think they're all getting quite close to 100% (or may even be at 100% with the 3.0 release). It's fine to mix PHP and Hack in the one project, so you could use a PHP framework and use Hack just for your code.
I noticed the other day that PHP has 30% code coverage. Is HHVM working to improve that (and pass the same tests, bug for bug) or is it relying on the unit tests of frameworks and packages?
>Can I get a better performance than my current setup of Nginx + uWSGI + Flask ?
That's really a bad question. It really all depends on where your bottleneck is. If you're benchmarking "Hello World" HHVM will be undoubtedly faster than Python/Flask. But if your bottleneck is in database/io, then you won't see much of a performance gain.
While the release names based on rappers is quite a fun idea, I don't get why they didn't go for people who are, you know, good at hip hop. I mean 50 cent and Childish Gambino? And especially next to Em and Ghostface. Or is this a good release/bad release kind of thing?
We have an on-call rotation in which one person has the job of cutting (and testing) the internal named release. That person has final choice for the name, often subject to lobbying by the more rap-enlightened members of the team.
Quick sidequestion: Does HHVM support the Weakref extension?
I ask because while it is not listed on the github wiki[1] but does appear in the manual[2]. I'm assuming the manual is an oversight, branched from PHP's manual and not pruned.
That said, weak-references are indispensable for certain problems, and I'd love to see them standard.
If you click on any of the methods in the manual, you'll see "NOT SUPPORTED IN HHVM" in a large font. I'm guessing it's an oversight that that text is missing from the topic index as well.
Same with Eminem. He and Dre are obsessive in their work. "In 2006, Snoop Dogg told the website Dubcnn.com that Dr. Dre had made new artist Bishop Lamont re-record a single bar of vocals 107 times." [1]
I know they can be considered bad practice, but in practice you use at at least a couple of them at least once in every project! And you use it because the alternative would be even uglier. (Also, what's the point in having a language with a separate namespace for functions and variables - Perl and Common Lisp being the only other ones I know of - if you can't at least have fun with variable variables and using a string directly as a function :) )
...also, they've "downgraded" PHP's closures mechanism. I mean, with:
...PHP managed to do things better then all other dynamic languages - finally a way of being explicit about what variables from the outer scope you drag into a closure! The Hack guys totally missed the point - they've made everything stricter, but they relaxed this constraint and reverted one of the few good ideas in PHP.Their VM may be awesome, but their language is horrid - they take away the "fun" features of PHP but don't fix any of the bad language design issues. It's like throwing away the baby and keeping the bath water - yeah, the water will keep you alive for a few more days in the desset, but the baby can actually be fun to play with.