News for hackers. Stuff that matters.
Re:Impressions of Go by pjmlp on Tuesday July 23, 2013 @03:12PM (#6092250)
My too, that is what made me stop playing with Go and look forward to D and Rust.

Initially Go attracted me, mainly because of the Oberon-2 influences (method declarations) and being compiled by default to native code. Java and .NET have AOT compilers, but don't tend to be used that much.

I even tried to do some initial contributions before the 1.0 release, but with time I got a Java 1.0 feeling. The language just throws too much away in the days that the enterprise is adopting Scala, Clojure, F# into their ecosystems.

I wish all the best to Go developers, but personally I don't think the language would be all the time here, if it wasn't being done at Google.

I mean, how often was Limbo discussed here, if ever?

Re:Impressions of Go by pron on Tuesday July 23, 2013 @03:28PM (#6092361)
Yes. Rust is an entirely different beast. A truly modern C-level language is something to look for.

There's no doubt Go wouldn't have been discussed here if it hadn't been done at Google. It's a really nice language, and the tooling is nice as well (far better than other new non-corporate-sponsored languages), but it doesn't address a need like Rust, or offer a way to tackle the hardest modern software development problems like Erlang or Clojure. As a language, it's not interesting either (say, like Haskell). It's not even a modern Java (like Kotlin). It's just Java. (only severely handicapped but made a little friendlier)

Then again, all this might not matter. Go is well executed, it's easier for Python devs to adopt than Java, and it's made at Google. And Google is known for making popular Java flavors, so, if Go's particular (few) strengths appeal to some -- why the hell not? There are smart people behind it, and I'm sure we can learn from Go, too.

Re:Impressions of Go by kibwen on Tuesday July 23, 2013 @03:52PM (#6092487)
I don't think it's fair to say that Go doesn't address a need. I volunteer on the Rust project, and compilation time of the compiler itself is one of the biggest problems at the moment. Take a look at at the turnaround times on our automated testing bots:

http://huonw.github.io/isrustfastyet/buildbot/

That's 24 minutes spent compiling each and every pull request! Granted, this is triply exacerbated by the fact that as a self-hosted compiler we have to compile three times, but I'd kill for sub-minute turnaround times for even a single stage (on a beefy dev machine we're down to maybe four minutes per stage, so 12 minutes total). We're putting a lot of focus on reducing this burden for our next release, but that's still time that could have been spent on features.

As I understand it, Go is intended to address this need for systems at Google's scale, where compilation presents enormous time overhead. I'm not a Go user so I can't comment on how well it achieves this, but one way or the other I think it's a really fascinating thing to optimize a language for.

Re:Impressions of Go by pjmlp on Tuesday July 23, 2013 @04:06PM (#6092569)
Rust suffers from having to compile LLVM as build dependency.

This will surely improve when Rust no longer requires it.

Go compile times are sweet, true. But Modula-2 and Pascal dialect compilers were already achieving similar compile speeds in 16 bit compilers a few decades ago.

Young developers get impressed by Go compilation times because they never experienced those systems.

Re:Impressions of Go by kibwen on Tuesday July 23, 2013 @04:16PM (#6092618)
Those compile times don't include building LLVM, which, on the rare occasion that a recompile is necessary, will add about five minutes on a beefy desktop and about an hour on our buildbots.
Re:Impressions of Go by pron on Tuesday July 23, 2013 @03:57PM (#6092522)
Sure, Go compiles a lot faster than C++, but unlike Rust, Go doesn't operate at the same level as C++, but at the same level as Java. How much faster does Go compile than Java?
Re:Impressions of Go by bjeanes on Thursday July 25, 2013 @12:30AM (#6100932)
I'm pretty sure the compilation time is less to do with the "level" that it operates. From presentations on the topic, most of the time savings were by making the syntax completely unambiguous. Apparently, in C/C++ and similar, some of the longest parts of the compilation process are lexing/parsing/AST-building, etc

(citations needed)

Re:Impressions of Go by manveru on Wednesday July 24, 2013 @02:45AM (#6094812)
Go pretty much compiles and runs within the time the JVM needs to even start.
Re:Impressions of Go by pjmlp on Wednesday July 24, 2013 @03:40AM (#6094939)
Which JVM?