Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Naturally having to pay for compilers isn't something that Go folks would ever do.


You’re deliberately ignoring my point and then throwing in an ad hominem for good measure. It has nothing to do with free or non free.

I ran a Java enterprise company for twenty years. I looked at AOT on multiple occasions, starting with gcj 20 years ago, and most recently, GraalVM. There were plenty of commercial compilers in between.

If there had been a non free AOT compiler that didn’t come with a bunch of compatibility and licensing complexities we would certainly have considered it. Just like we bought non free IDEs.

But such a tool didn’t exist. The cost in missing features and added complexity was always much greater than the sticker price.

Java AOT is an afterthought, it is not at all comparable with Go AOT, which is a core feature of Go, expressed for example in the Go team’s explicitly designing the language itself to support fast compilation.

There are plenty of conversations to be had where we can compare the two languages, Go will not always win those discussions, but one of the inarguable features of Go is that it is AOT from the ground up, and that is a feature that’s really valuable to me.


First you accuse me of ad hominem, and then confess that you only cared about free AOT compilers for Java, gcj which the only feat was being able to compile Eclipse with some nurturing quickly abandoned in 2009, while ignoring the commercial offerings that have been available for 20+ years.

Good job.


WTF? I said “from” gcj, the earliest AOT compiler that I know about, “until” graalvm, the most recent that I know about, and that “There were plenty of commercial compilers in between”.

Please stop.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: