3 ms·
The state of natively compiled GC'd languages is actually pretty bad, at least ones with an ecosystem/job opportunities. You either have to run into the same p
by vips7L 6y ago
The state of natively compiled GC'd languages is actually pretty bad, at least ones with an ecosystem/job opportunities.
You either have to run into the same problem as dark when it comes to libraries and ecosystem (ocaml, haskell, D, etc), use go and give up any nice language features, or run on a VM and deal with all the issues of packaging/weight (clr, jvm).
- pjmlp 6y agoWhen packaged alongside the binary, VM for all purposes is just the language runtime,e.g. natively compiled Java.
- vips7L 6y agoI just don't think natively compiled Java is there yet. It's not trivial to get it working and the ecosystem isn't ready for it yet. There are certain things that just work (i.e. quarkus, which I have a web service running on 13 mb of ram), but I have never been able to successfully compile to native on my own because of library dependencies. Getting things like Weld or H2 to work is pretty difficult.
- pjmlp 6y agoIt is there since 2000. AOT compilation has been a feature of most commercial JDKs, specially the ones targeted at embedded development like PTC and Aicas.
- aphexairlines 6y agojlink potentially helps with weight.