[gregoriol]

Reminds me of HHVM: a specific solution developed by a specific team for their specific problem.

Might help Redis on the long run though: some ideas might be brought back to Redis, or at least it will bring some challenge to the devs.

Meanwhile, keep calm and use Redis ;-)

[ianlevesque]

Agreed, though HHVM went on to be deployed at some other small websites [1]. Maybe this will too.

1. http://hhvm.com/blog/7205/wikipedia-on-hhvm

[mintplant]

On the other hand, Wikipedia is going to have to migrate back off of HHVM now that Facebook is planning to break compatibility with PHP and focus totally on Hack [0]. So hopping on board someone else's solution can bite you if their priorities change.

[0] http://hhvm.com/blog/2017/09/18/the-future-of-hhvm.html

[justinsaccount]

> Facebook is planning to break compatibility with PHP and focus totally on Hack

Ok...

> Wikipedia is going to have to migrate back off of HHVM

Why?

[e1g]

For years, HHVM had a significant edge in performance and a significant handicap in compatibility. Today, PHP7.1+ is ~at parity in performance but the community still has not fully embraced HHVM. In fact, some flagship projects like Symfony even stopped on purpose. Increasingly, the main reason remaining for running PHP on HHVM is if you really want static typing - and this is not a natural preference for most PHP teams.

[mintplant]

Hack/HHVM is breaking compatibility with PHP. MediaWiki is a large PHP software project. Other MediaWiki users run the software in non-HHVM environments.