You can't compile C to java bytecode, they are fundamentally incompatible. But you can compile C to wasm, which is what you want for a good universal bytecode. Java is shit.

[+] onlinepersona@programming.dev -8 points 7 months ago (4 children)

May I introduce you to https://github.com/davidar/lljvm

The C to JVM bytecode compilation provided by LLJVM involves several steps

[–] pftbest@sh.itjust.works 4 points 7 months ago (1 children)

Have you seen what it outputs? The same way we can compile C to brainfuck, it doesn't mean it's good or is useful.

[+] onlinepersona@programming.dev -8 points 7 months ago (1 children)

"compiling C to java bytecode isn't possible"
*link to project that does exactly that*
"it's not good or useful"
*WASM exists*
"that's useful"

... OK

Anti Commercial AI thingy

CC BY-NC-SA 4.0

[–] pftbest@sh.itjust.works 0 points 7 months ago (1 children)

I can't quite understand what is your point? Are you arguing that both JVM and WASM are bad? With this I agree, they both have terrible performance and in an ideal world we wouldn't use any of them.

Are you arguing that JVM bytecode is better than WASM? That's objectively not true. One example is a function pointer in C. To compile it to JVM bytecode you would need to convert it to the virtual call using some very roundabout way. But in WASM you have native support for function pointers, which gives much better flexibility when compiling other languages.

load more comments (2 replies)

load more comments (4 replies)