71–80 of 110 posts
I tried in vain to find WebAssembly. Why would you include JavaScript but not WebAssembly in a graph that has LLVM in it?
It does have WebAssembly, but its incorrectly labeled as targeting Java Bytecode.
My main takeaway: people want to avoid writing JavaScript about as much as they want to avoid writing machine code or Java bytecode.
It's just that, at least for the first couple decades of its existence, the platform in question had no bytecode, so transpiling was the only way to escape.
My main takeaway: people want to avoid writing JavaScript about as much as they want to avoid writing machine code or Java bytecode.
A few missing items: - CIL to C++ using CoreRT/AoT compiler [1] - JVM to CIL using ikvmc [2] - Quite a few languages to WebAssembly using LLVM [3] - J# if you are willing to include dead but somewhat significant languages [1] https://blogs.msdn.microsoft.com/alphageek/2016/10/13/native... [2] http://www.ikvm.net/userguide/ikvmc.html [3] https://stackoverflow.com/questions/43540878/what-languages-...
Where is Smalltalk ?
So, you can apparently compile C++ to LLVM-IR, then to Javascript, then to Python and then to C++ (you can do similar feat with C). Wonder if there is a fix point, or it diverges.
Like when you auto-translate English -> Japanese -> English. Very unlikely you will recover the original Good fun though.
Interactive graph is nice, but what's with so few zoom levels? It's either too small or too large.. Or is my mouse scroll wheel too sensitive?
Earlier quoted context omitted.
> given that the machine code is an intermediate product The machine code isn't the intermediate product - it's the final product. Some internal IR is the intermediate product. But yes it's normal convention in the industry to talk about JIT compilation to machine code as 'compiling to machine code'.
But let's say, they added "decompilers" to the graph, and there is (say) a decompiler from machine code to C. Then I'd assume, because there is a path in the graph from JavaScript to C (going through machine code), that I can translate from JavaScript to C. Except this isn't true because V8 is a JIT, and doesn't output its internal representation.
You mean that the JavaScript compilation is only valid for a given application at a given point in time? Yes that's true.