It is relative. If a project only pushes a few commits a year, 2 months of quiet is nothing. Given this project going to zero commits from 100s of commits a week is noteworthy.
Hi, Paul from the Open Source Team here at Meta. HHVM is still in use and there are no changes to the level of maintenance the open source project gets. There's no conspiracy, no quiet quitting. The reality is that we just had some issues that affected our automatic syncing a little while back and HHVM got stuck. Since use outside of Meta is relatively low, unsticking it was just lower priority.
But we see that you've noticed and I think the folks working on HHVM internally will get that corrected soon!
I'm a little surprised HHVM is still around, last time I checked it was barely (if at all) faster than vanilla PHP and PHP now has a lot of the comparible features like progressive type safety and concurrency (to an extent).
There are even competing PHP compilers/interpreters/runtimes now like there has been for a while with other languages.
I'm guessing there is some benefit to running HHVM on the type of large scale deployments Facebook has or there wouldn't be a need to keep it around.
Generally yes but the languages are similar enough that the refactoring could be automated. Of course, that would create a fair amount of QA and testing work but if you have good test coverage you can mitigate that.
I find it interesting that it’s still getting a few github stars monthly[1]. I wonder if that’s organic discovery or an appetite for an alternative PHP?
From what I understand it is still a quite popular language at meta, and strongly supported and preferred for lots of development, though definitely never got much traction externally.
It seems to me that this project is still being maintained and it isn't archived, if it is not maintained and not archived then it would present a problem.
This really does not come as a surprise. PHP 7 erased the performance gains that Hack had, and PHP 8 brought a lot of the last few missing pieces that helped modernize PHP.
Hack was heavily optimized for Facebook-sized setups and was never intended to run in the places that PHP is most often run from (such as cPanel servers), so it never really picked up much traction among the PHP world.
Non-PHP developers never even considered it as an option, as they probably didn't consider PHP as an option either.
Basically, it was one of those projects that may have been a good idea when it was released (although perhaps just contributing more to PHP might have been the better thing for Facebook to do, but that's a different story), and it's time has now passed. I'm just surprised it took this long for them to end work on it, honestly
Huh, I'm surprised by that take. await is one of the easiest-to-comprehend and readable approaches to concurrency. Slack summarized this better than I can, see the async/await section of their post https://slack.engineering/hacklang-at-slack-a-better-php/
Without async/await, PHP will remain a bad fit for large-scale applications that need to query data from numerous distinct services or data stores for a single page load without incurring major latency. It was an absolutely essential feature of Hack at Facebook. Lack of async/await in PHP was a huge problem at Tumblr when trying to reduce latency.
Not to be terse, but did anyone outside of FB ever care about Hack? Mentally I always just knew "FB built everything in PHP, it got too gunky, they invented Hack to try to solve the issue without needing to rewrite everything"
PHP usually ranks pretty high on many "developer hate" polls, so it's not too shocking to me that Hack never got the hype of React or Golang.
I worked on Hack during my Meta bootcamp and was surprised to learn that many people used and relied on Hack outside of Meta. It didn’t appear to be anywhere near the size and scope of PyTorch and React but the number of users looked relatively large!
Alternate anecdata, I've never seen someone use it outside of Facebook/Meta. I'm sure some people did but PHP 7 solved the performance issues people had with PHP 5, and PHP 8 nuked some of the footguns people complained about all the time, to the point, the few shops who looked at Hack / HHVM (and weren't switching to another language entirely) just stayed on PHP.