Orm: HHVM support

Created on 5 May 2017  路  11Comments  路  Source: doctrine/orm

We're struggling to support HHVM properly on our projects:

So it's time to rethink if we still want to guarantee HHVM support, the reasons are:

  1. Even though we managed to run HHVM 3.15 on travis it was impossible to install the dependencies (we should give it a try on HHVM 3.18 however I'm not sure how often HHVM users upgrade stuff)
  2. We want to use new PHP features but HHVM is not being able to keep up the pace updates and they still have a list of PHP 5 and 7 incompatibilities
Improvement

Most helpful comment

Overall, I feel bad for dropping HHVM support, but lack of latest versions by default on CI, as well as incompatibilities with PHP 5, 7, 7.1 are starting to become an issue. Community usage is also very low, since PHP 7 made most interactions as fast as on HHVM.

We need to drop it though, as we need to bump the minimum version to PHP 7.1 anyway.

All 11 comments

Overall, I feel bad for dropping HHVM support, but lack of latest versions by default on CI, as well as incompatibilities with PHP 5, 7, 7.1 are starting to become an issue. Community usage is also very low, since PHP 7 made most interactions as fast as on HHVM.

We need to drop it though, as we need to bump the minimum version to PHP 7.1 anyway.

Pinging @Seldaek - he did publish some HHVM stats from Packagist a while back and mentioned in IRC he'd post some current numbers soon. Quote:

last I checked it was less hhvm than php5.3 IIRC

Here: https://github.com/composer/composer/issues/6230#issuecomment-284426560

last time I checked there was less HHVM than PHP 5.3 users of composer, about 0.4% or smth IIRC, so not really worth the trouble I would say.


Maybe someone from Facebook could share their vision regarding compatibility, but it's been years and even many PHP 5 bugs are still unfixed, not even taking 7.0/7.1 into consideration. There is still ~250 open issues marked _PHP 5 incompatibility_ and another ~75 marked _PHP 7 incompatibility_. There are also 43 issues marked _wontfix_ which are _PHP 5 incomatiblities_.
I initially sent some bugfixes and another bunch of issues to HHVM, but now I just have a feeling that HHVM has its own path with PHP compatibility not being a priority.

Btw Symfony still seems to actively ship HHVM support, it'd be interesting to know their point of view, regarding HHVM + Symfony 4.

@Majkl578 Symfony doesn't provide any guarantee for HHVM, but accept fixes for it. Cf. https://github.com/symfony/symfony/issues/18922

@theofidry: Thanks for the link; Symfony doesn't have HHVM in allowed failures so they apparently still do care enough. :)

@Ocramius since we had a blogpost about the HHVM roadmap should we write something again?

Laravel doesn't follow HHVM since: https://github.com/laravel/framework/pull/14530

It could be dropped for version 3 and reintroduced if there really will be a demand. Something I highly doubt, of course.

I believe this project does not need things dragging it down and that what HHVM support currently is - a minor feature requiring a lot of work, postponing important features.

I actually don't think this would have to wait for next major. Similarly to the PHP versions which are dropped/bumped in minor versions too...

Handled in #6507 (for ORM)

Was this page helpful?
0 / 5 - 0 ratings