HHVM VS AECforWebAssembly

Learned of this in https://news.ycombinator.com/item?id=37186869 it was posted 2 years ago to no discussion https://news.ycombinator.com/item?id=30291459 seems far more interesting than that.

https://github.com/facebook/hhvm/blob/master/hphp/hack/doc/H... appears to be where it was proposed, and has more background than the current docs.

also fredemmott is not working on it any more https://github.com/facebook/hhvm/issues/9376

Hack and Flow are also written in OCaml.

Here is a commit generated by clippy fix without Cargo involved: https://github.com/facebook/hhvm/commit/efea2c4dcc12fdbf3a2e3ce383bbdca2de5f93a9

Compared to PHP, with its visible community, Hack/HHVM does seem like a dead-end technology. But it’s very actively maintained and it powers the largest website on the planet. It definitely doesn’t make sense for the average PHP developer to switch (and the article steers clear of evangelising) but it also definitely doesn’t make sense for us to switch back.

PHP is nearly as old as the web. Change the conversation and say: I use Hack on the Hip Hop Virtual Machine

Great! I have not yet made source maps for my programming language that compiles to WebAssembly, and I probably never will.

Up until today, my AEC-to-WebAssembly was, if somebody tried to use two structures of different types as the second and the third operand to the ?: (ternary conditional) operator, as in this example: ``` Structure First Consists Of Nothing; EndStructure

Well, I have written the first compiler for my programming language, targetting x86, in IE6-compatible JavaScript, and the second compiler, targetting WebAssembly, has been written in C++11. I think that, to choose a language to write a compiler in, you need to look at at least two things:

You can see the releases v2.5.3 and v2.5.2 of AECforWebAssembly on GitHub. They are produced with the same version of GCC, the only difference (as far as I know) is that v2.5.2 was produced directly on Debian, whereas v2.5.3 was cross-compiled from Windows to Linux using Docker.

That could be true. I host my AEC-to-WebAssembly compiler on GitHub, GitLab and SourceForge, and it's only on GitHub that it has 21 stars and 2 forks. On GitLab and SourceForge, it has zero of both.

Well, the main compiler for my programming language is targetting the JavaScript Virtual Machine by outputting WebAssembly. I think it's even better than targetting Java Virtual Machine, because, for one thing, your executables can run in any modern browser if you output WebAssembly. If you target Java Virtual Machine, the users need to actually download your app. Furthermore, there is an official assembler for WebAssembly called WebAssembly Binary Toolkit (WABT), so your compiler can output assembly and not have to deal with binary files. There is nothing equivalent to that for Java Virtual Machine.