pftbest

joined 1 year ago
[–] pftbest@sh.itjust.works 3 points 4 hours ago

This is a very dangerous way of thinking. You cannot tell at the time of discovery if specific research will be useful or not down the line. You need to advance the research in all directions, even if some of them seem silly or useless, or else you will handicap your progress in other fields which you didn't see the connection with at first.

[–] pftbest@sh.itjust.works 3 points 1 month ago

1.5 ton aluminum bar, chilled to absolute zero. This would be a massive project to setup

[–] pftbest@sh.itjust.works 3 points 1 month ago

Funny you mentioned arch, as steam deck os is based on arch, so it is using arch btw

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

It's the other way around, you will get all of the tickets which are missing plate info. Some guy did it and regrets it, there is a documentary about it.

[–] pftbest@sh.itjust.works 2 points 6 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.

[–] pftbest@sh.itjust.works 7 points 6 months ago (3 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.

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

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.