A graph of programming languages connected through compilers • Hacker News Board

Re: A graph of programming languages connected through compilers

#61

Post by macintux » Fri, Jul 06, 2018, 1:40 PM UTC

joseluisq wrote: post #30

Where is Smalltalk ?

Probably hiding the same place as the BEAM languages. No Erlang, Elixir, etc.

Re: A graph of programming languages connected through compilers

#62

Post by azhenley » Fri, Jul 06, 2018, 1:46 PM UTC

Is this a challenge to see if we can make this a fully connected graph?

Re: A graph of programming languages connected through compilers

#63

Post by ThJ » Fri, Jul 06, 2018, 1:48 PM UTC

I tried in vain to find WebAssembly. Why would you include JavaScript but not WebAssembly in a graph that has LLVM in it?

Re: A graph of programming languages connected through compilers

#64

Post by kevin42 » Fri, Jul 06, 2018, 1:51 PM UTC

It seems like there is a lot missing from this graph. There's a ton of info for conversion to javascript here:

https://github.com/jashkenas/coffeescript/wiki/list-of-langu...

Re: A graph of programming languages connected through compilers

#65

Post by hiimnate » Fri, Jul 06, 2018, 1:52 PM UTC

ThJ wrote: post #63

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.

Re: A graph of programming languages connected through compilers

#66

Post by Keyframe » Fri, Jul 06, 2018, 1:53 PM UTC

Dude, where's my lisp?

Re: A graph of programming languages connected through compilers

#67

Post by bamboo_7 » Fri, Jul 06, 2018, 1:54 PM UTC

bjpirt wrote: post #55

drtz wrote: post #51

My main takeaway: people want to avoid writing JavaScript about as much as they want to avoid writing machine code or Java bytecode.

Alternative takeaway: Javascript is so widely deployed that most languages have found a way to compile to it

Alternativev (joke) takeaway: Javascript is as important to computers as machine code

Re: A graph of programming languages connected through compilers

#68

Post by [deleted] » Fri, Jul 06, 2018, 1:55 PM UTC

bjpirt wrote: post #55

drtz wrote: post #51

My main takeaway: people want to avoid writing JavaScript about as much as they want to avoid writing machine code or Java bytecode.

Alternative takeaway: Javascript is so widely deployed that most languages have found a way to compile to it

[deleted]

Re: A graph of programming languages connected through compilers

#69

Post by chrisseaton » Fri, Jul 06, 2018, 1:56 PM UTC

hiimnate wrote: post #65

ThJ wrote: post #63

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.

> incorrectly labeled as targeting Java Bytecode

https://github.com/cretz/asmble

The name of that tool is even labelled in the graph!

Re: A graph of programming languages connected through compilers

#70

Post by amelius » Fri, Jul 06, 2018, 1:57 PM UTC

chrisseaton wrote: post #56

amelius wrote: post #44

It says V8 compiles JavaScript to Machine Code, but is that really correct given that the machine code is an intermediate product, and the result of applying a JIT to a specialized piece of code (where part of the variables are already known to the compiler)?

> 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.