News for hackers. Stuff that matters.
Re:Go best practices, six years in by MichaelGG on Monday May 02, 2016 @04:51PM (#11615484)
Don't be disappointed. If you don't need the performance Rust offers, then use another ML-ish language. More expressiveness, none of the ownership issues (just GC).
Re:Go best practices, six years in by weberc2 on Monday May 02, 2016 @04:59PM (#11615558)
Which would you recommend for someone who prefers a C-like syntax, a good concurrency story, a comprehensive standard library, Java-esque speed, and dead-simple tooling (e.g., Go's tooling), and compilation to a static binary?
Re:Go best practices, six years in by MichaelGG on Monday May 02, 2016 @05:43PM (#11615929)
C# and F# can both compile to a static binary (Mono's AOT compiler), and meet your other requirements. I find it curious that "safety" wasn't one of the points.

If you're looking for C-like though, you are probably not in any modern-featured language designer's aim.

Re:Go best practices, six years in by weberc2 on Tuesday May 03, 2016 @09:44AM (#11620533)
> I find it curious that "safety" wasn't one of the points

It was implied by the context of "ML" languages. That was my intention at least; I thought ML languages were characteristically safe.

Regarding "C-like", I mostly mean syntax. I'm not too familiar with the ML family, but many FP languages have bizarre syntax which amplifies the difficulty of learning new concepts IMO.