Re:Blink-dev – Intent to Ship: SharedArrayBuffer
by josefx on Friday April 07, 2017 @10:19AM
(#14059825)
There are coprocessors that run Java Bytecode directly. Is there actually an implementation of the machine outlined in the C standard? Clearly C is an abstraction while Java is a truly native language.
[ Parent
| on HN ]
Re:Blink-dev – Intent to Ship: SharedArrayBuffer
by voxic11 on Friday April 07, 2017 @10:57AM
(#14060202)
Well those processors just run bytecode compiled from Java source code. The same is true of more traditional processors they just run bytecode compiled from c source code. I thicnk they are both doing essentially the same thing.
Re:Blink-dev – Intent to Ship: SharedArrayBuffer
by josefx on Friday April 07, 2017 @01:49PM
(#14061894)
So what are the properties of C bytecode? Other than undefined, implementation defined and format C:\\ ? Java specifies a high level language, the low level bytecode and a target machine while C has to abstract over the byte code and large parts of the machine, leaving it up to the developer to fight countless "implementations". Guaranteeing that the same code is simultaneously right, wrong and file not found while limiting access to features exposed by the underlying "bytecode" in ways that require software workarounds like fmadd that are used in place of hardware.
Clearly the Java language -> Java bytecode -> Java Hardware chain is inherently more native and consistent than C language -> C Virtual Machine -> x64 -> Intel Core 2, where each step in the C language chain looses access to features of the underlying layer.