23 ms·
That still gives you Lisp, Ada, Go, Haskell, and Java, if you make the (imo incorrect) assumption that "low level" tools can only be written in languages which
by falcolas 11y ago
That still gives you Lisp, Ada, Go, Haskell, and Java, if you make the (imo incorrect) assumption that "low level" tools can only be written in languages which compile down to bytecode.
Of course, Mercurial gives lie to this assumption.
- samirm 11y agoJava? You won't get any performance out of it compared to something like C.
- pjmlp 11y agoIn what scale? What it matters is if it is fast enough for the use case being targeted. As side note I remember when C compilers for home computers generated worser code than junior Assembly programmers.
- joushou 11y agoI don't like Java, but don't underestimate the performance of the JVM. Unless you're a crazy perf wiz, then your average C code won't beat your average Java code. It's fast enough for short processes, and for long processes the JIT is pretty darn good. Also note that a JIT can perform runtime assumptions and optimize code based on what is currently the case, which an AOT compiler cannot. It takes a lot more than a toolchain to write fast code.