Learning Go by porting a medium-sized web back end from Python

Re:Learning Go by porting a medium-sized web back end from P... by oblio on Thursday November 09, 2017 @05:15AM (#15661248)

Yeah, but Kotlin Native loses all the Java libraries. The more interesting thing would be Java native compilation coupled with Kotlin. So you'd write a Kotlin Java app and pass that through the Java native compiler introduced in Java 9. Unfortunately that's a beta feature right now, I think it only supports Linux x64, that's why I said Kotlin 2019, I assume that by then the Java native compiler will support all Java platforms.

[ Parent | on HN ]

Re:Learning Go by porting a medium-sized web back end from P... by pjmlp on Thursday November 09, 2017 @05:33AM (#15661326)

Java compiles to native code since version 1.0, only not for free.

All commercial JDKs had this option in one form or the other, and many of them are still around.

If you want to try this for free on open source projects, Excelsior JET is one option.

[ Parent | on HN ]

Re:Learning Go by porting a medium-sized web back end from P... by oblio on Thursday November 09, 2017 @05:41AM (#15661352)

I'm probably too conservative, but I'd rather use these kinds of things from the actual platform developers. I'm a bit more liberal with libraries, but in general I want the compilers/interpreters from the upstream source. Software has enough bugs as is :)

[ Parent | on HN ]

Re:Learning Go by porting a medium-sized web back end from P... by pjmlp on Thursday November 09, 2017 @06:33AM (#15661559)

Commercial JDKs, like from IBM or OEMs for embedded platforms, are the actual platform developers.

[ Parent | on HN ]

Re:Learning Go by porting a medium-sized web back end from P... by mhd on Thursday November 09, 2017 @10:31AM (#15663197)

> Java compiles to native code since version 1.0, only not for free.

Well, there was GCJ, but I think that hurt more than it helped.

[ Parent | on HN ]