Rust vs. Go - Hackdot

Re:Rust vs. Go by geodel on Wednesday January 18, 2017 @05:54PM (#13431232)

Shenandoah has pause times ~10ms and is recommended for heaps 20GB+ for vs sub millisec in Go. NTPSec does not seem to have such high end memory requirements. Also now Java based app will need JVM availability on all platforms where NTPSec runs.

I think sometimes it makes sense not to shove Java where it is not applicable.

http://www.slideshare.net/RedHatDevelopers/shenandoah-gc-jav...

[ Parent | on HN ]

Re:Rust vs. Go by mike_hearn on Thursday January 19, 2017 @04:04AM (#13434251)

Yes, but that's because it's only really large heaps where pause times become problematic. On small heaps even dumb algorithms can give tiny pauses (a few msec or less) on modern hardware.

It's true you'd need a JVM on the platforms where ntpsec runs but that's also true of having a port of the Go runtime.

[ Parent | on HN ]

Re:Rust vs. Go by hnbro on Wednesday January 18, 2017 @09:07PM (#13432362)

can go (or rust) compile for targets that don't have a jvm?

[ Parent | on HN ]

Re:Rust vs. Go by mixedCase on Thursday January 19, 2017 @01:10AM (#13433490)

As far as Go goes, I believe neither the Plan 9 OS nor the MIPS CPU architecture have a production-ready JVM. Go supports both.

[ Parent | on HN ]