3 ms·

Thank you for your work on this and for open sourcing it. It looks like it can make large code bases in PHP a great deal more manageable. Do you expect Hack to

Thank you for your work on this and for open sourcing it. It looks like it can make large code bases in PHP a great deal more manageable. Do you expect Hack to be stable without large breaking changes going forward? The documentation doesn't say much about the scheduling for asynchronous tasks. Can async functions be used to batch requests to e.g. caches and databases? Can Awaitable be used to interface with code that expects chainable Future or Promise-style interfaces? Can HHVM/Hack use standard PHP extensions, or how much work is it to port an extension? Is there a Hack plugin for IntelliJ? Does the Hack project have a mailing list or forum?

SaraMG 13y ago
"Can HHVM use standard PHP extensions?" Our internal plumbing is different, so the extension APIs aren't the same, thus PHP extensions can't normally be used with HHVM. Paul has a source-compatability transformer which works for simple extensions (no fancy stuff allowed), but we recommend anyone with an extension consider porting the code. If your extension is one of those "This was written in PHP but we wanted it to be faster so we turned it into C" types, you should consider going back to PHP for it. In practice, we find that HHVM can JIT PHP code into running about as fast as (sometimes faster than) C/C++ extension code. If you do need to dip into C/C++ (because you're calling an external library), the API we've designed is a LOT easier to work with than PHP's. And I say that with the authority of having written THE book on writing PHP extensions: http://amazon.com/dp/067232704X http://amazon.com/dp/067232704X . I'm working on proper documentation for extensions as we speak, but for now you can find some very basic info at https://github.com/facebook/hhvm/wiki/Extension-API https://github.com/facebook/hhvm/wiki/Extension-API .

SaraMG 13y ago

"Can HHVM use standard PHP extensions?" Our internal plumbing is different, so the extension APIs aren't the same, thus PHP extensions can't normally be used with HHVM. Paul has a source-compatability transformer which works for simple extensions (no fancy stuff allowed), but we recommend anyone with an extension consider porting the code. If your extension is one of those "This was written in PHP but we wanted it to be faster so we turned it into C" types, you should consider going back to PHP for it. In practice, we find that HHVM can JIT PHP code into running about as fast as (sometimes faster than) C/C++ extension code. If you do need to dip into C/C++ (because you're calling an external library), the API we've designed is a LOT easier to work with than PHP's. And I say that with the authority of having written THE book on writing PHP extensions: http://amazon.com/dp/067232704X http://amazon.com/dp/067232704X . I'm working on proper documentation for extensions as we speak, but for now you can find some very basic info at https://github.com/facebook/hhvm/wiki/Extension-API https://github.com/facebook/hhvm/wiki/Extension-API .