Dark’s new backend will be in F#

Re:Dark’s new backend will be in F# by vips7L on Tuesday November 03, 2020 @11:16AM (#24980942)

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).

[ Parent | on HN ]

Re:Dark’s new backend will be in F# by pjmlp on Tuesday November 03, 2020 @12:07PM (#24981515)

When packaged alongside the binary, VM for all purposes is just the language runtime,e.g. natively compiled Java.

[ Parent | on HN ]

Re:Dark’s new backend will be in F# by vips7L on Tuesday November 03, 2020 @12:25PM (#24981706)

I 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.

[ Parent | on HN ]

Re:Dark’s new backend will be in F# by pjmlp on Tuesday November 03, 2020 @01:22PM (#24982373)

It 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.

[ Parent | on HN ]

Re:Dark’s new backend will be in F# by aphexairlines on Tuesday November 03, 2020 @04:00PM (#24983915)

jlink potentially helps with weight.

[ Parent | on HN ]