News for hackers. Stuff that matters.
Re:Toward Go 1.3 by joncooper on Tuesday February 11, 2014 @01:00PM (#7219044)
Totally agree. Go is a superb systems language. But I wouldn't use it for a CRUD web app, nor for quasi-exploratory data pipelines, which is where IMO such generic functional combinators are clutch. It is however awesome when you've nailed down the data pipeline and you want to get a big speed improvement in a fraction of the time required to build out in C/C++.
Re:Toward Go 1.3 by Buttons840 on Tuesday February 11, 2014 @06:07PM (#7221207)
What makes Go a good "systems language"? Is it because it's fast? What about Java, Scala, Clojure, Haskell, C#, F#, Scheme, Ocaml, etc, which all have performance (speed of execution) similar to Go, are they good "systems languages" as well?

If it's not speed of execution then what makes Go a good systems language? The ability to fiddle bits? A small runtime?

Re:Toward Go 1.3 by amalag on Tuesday February 11, 2014 @07:46PM (#7221719)
One thing is gochannels and the lightweight concurrency primitives.
Re:Toward Go 1.3 by codygman on Tuesday February 11, 2014 @11:48PM (#7222559)
Java, Scala, Clojure, Haskell, C#, F#, Scheme (do Rackets Places count?) all have their equivalents.
Re:Toward Go 1.3 by ghayes on Tuesday February 11, 2014 @02:28PM (#7219779)
I would use it for a CRUD app and I wish it had features that would support that. As an open-language, this input should be considered (alongside the input of the maintainers and other users of the language). I believe the top-comment here was saying that this conversation shouldn't be side-lined.