News for hackers. Stuff that matters.
Re:Introduction to Go 1.1 by tptacek on Tuesday March 26, 2013 @12:01PM (#5444152)
1. It clearly is a systems programming language. Pike has written whole articles about how difficult it has been to convince C++ people ot switch.

2. It clearly does have an extremely fast compiler.

3. It clearly is very fast, and Pike never claimed it was the fastest.

4. The GC works and is an active area of development. They are open about this. What do you want them to say?

5. Could you cite them actually saying Go was used all over Google?

Re:Introduction to Go 1.1 by pron on Tuesday March 26, 2013 @01:53PM (#5444934)
1. Maybe, depending how you define "systems programming language". Go, unlike Rust, is not really low level. Its just as "systems level" as Java is, and many C++ shops have switched to Java. So Go is like Java in that respect. Not a C/C++ replacement in the post-Java era.

2. Sure. Much faster than C++. But, as Go is really a Java alternative rather than a C++ alternative, the compiler is not that much faster than Java's.

3. Yes, but not fast enough as a C/C++ replacement. It's not even as fast as Java.

4. The Go team has made some interesting, and risky, design decisions with the GC. They write: "Go must support what we call interior pointers to objects allocated in the heap... This design point affects which collection algorithms can be used, and may make them more difficult, but after careful thought we decided that it was necessary to allow interior pointers because of the benefits to the programmer and the ability to reduce pressure on the (perhaps harder to implement) collector. So far, our experience comparing similar Go and Java programs shows that use of interior pointers can have a significant effect on total arena size, latency, and collection times." It will be interesting to see how this decision pans out.

5. I think he pretty much just did. Or, to be precise, he quoted what is likely a false prediction.

It is true that both Go and Rust were first touted as a C/C++ replacement. Go clearly isn't while Rust clearly is. Go is a Java alternative minus the dynamic code-loading, and as such, hardly revolutionary. You get similar compilation speed, a slower runtime and none of the dynamic stuff. Go is sure a nice language, but Java shops are better off moving on to Clojure or Scala if they need a better language.

Re:Introduction to Go 1.1 by tptacek on Tuesday March 26, 2013 @02:09PM (#5445035)
The Go compiler is much faster than javac.

I don't accept your premise of "Java is the floor for acceptable performance in systems programming languages". Plenty --- perhaps most! --- new serverside code is written in languages much, much slower than Java. I'm not sure if I accept your premise that Golang is consistently slower than Java (if it is, the difference is marginal). On the other hand, Golang code starts instantly and has no runtime requirement.

I'm peripherally aware of some kind of rivalry between Rust and Go, but I'm not interested in discussing it; I use programming languages as tools to solve problems, not as tribes to join. When Rust is ready for prime time, I'll check it out and see if it solves any of my problems better than C, Golang, or Ruby, and if it does, I'll start using it. I have no plans to take seriously the idea of benchmarking the whole of Go against the whole of Rust.

Re:Introduction to Go 1.1 by pcwalton on Tuesday March 26, 2013 @02:26PM (#5445142)
There is not really a rivalry between Rust and Go; they had different goals and Go is a fantastic language for its goals. For example, Mozilla uses both Rust and Go for different things. I don't see any need for tribalism either.
Re:Introduction to Go 1.1 by pron on Tuesday March 26, 2013 @02:32PM (#5445166)
All I'm saying is, Go was touted as a C/C++ replacement while it clearly isn't; it's a Java alternative, and as such, more than justifies comparisons of the two. When you compare them, you see some advantages for Go and some for Java.

I don't think there's a rivalry between Rust and Go, and if there is -- there shouldn't be. They serve completely different purposes: Go is an alternative to Java, while Rust is an alternative to C/C++. It's not about speed, either. It's about level of control.

Re:Introduction to Go 1.1 by tptacek on Tuesday March 26, 2013 @02:40PM (#5445208)
This stuff about Golang "touted" seems to turn on picky definitions "touting" that include "stating the objectives of the language project". But more importantly, they are just not relevant to developers.

So, having watched Rob Pike talk about Golang many times, and read a lot of what he's written about the language, I object to the way you're distilling what he's saying about the project. But, more importantly, I object to the sideshow.

Re:Introduction to Go 1.1 by pron on Tuesday March 26, 2013 @02:57PM (#5445314)
I'm not being picky, this isn't a sideshow, and I think it's very relevant to developers. As most "systems" developers are quite familiar with C and with Java, and Go is the new kid on the block, it is important to point out that Go essentially solves the same problems Java does, and not those that you'd turn to C to solve. This is especially important to point out because Go's objectives initially placed the language in the C space, or so it seemed to many.
Re:Introduction to Go 1.1 by tptacek on Tuesday March 26, 2013 @02:59PM (#5445331)
Let's agree to disagree that this is an important point.
Re:Introduction to Go 1.1 by burntsushi on Tuesday March 26, 2013 @06:44PM (#5446541)
> it is important to point out that Go essentially solves the same problems Java does

One of the major selling points of Go is its concurrency features built into the language. Namely, first class channels and lightweight threads. Java has neither of those. In particular, very few languages support lightweight threads in an M:N scheduling style (Haskell, Erlang, Rust), which in and of themselves makes Go a very attractive tool for concurrent programming.

Re:Introduction to Go 1.1 by pron on Tuesday March 26, 2013 @07:43PM (#5446772)
Actually, these aren't lightweight threads because, AFAIK, they require cooperative multitasking. Java actually has fork-join, an extremely sophisticated scheduler, that allows much finer control over scheduling than Go, and also supports non-cooperating tasks. I believe it's being used as the basis for Akka's actors. Java also has quite a few queue implementations suitable for a different concurrency scenarios. So, in that respect, Go offers easier to use, though fewer, concurrency options, while Java offers finer control over concurrency.

But the point wasn't to debate the merits of Go over Java or vice versa, just to say that they are both intended to be used in the same domains.

Re:Introduction to Go 1.1 by burntsushi on Tuesday March 26, 2013 @08:20PM (#5446939)
Go's lightweight threads do not require cooperative multitasking in the traditional sense. In Go, lightweight threads are preempted by the runtime whenever an operation that can block is made (IO, channel send/receive, system calls, etc.). However, lightweight threads can hog the CPU, and in that sense, they must be cooperative. But this rarely shows up outside of pathological cases in practice.

More importantly, I wasn't talking about scheduling. I was talking about lightweight threads. They are also commonly known as: goroutines, green threads, fibers, user space threads, etc. This has a dramatic effect on the style of concurrent programming, as spawning a light weight thread is cheap relative to spawning an OS thread.

Joe Armstrong explains [1] things better than I can:

    Processes in Java or C# are pretty much like the objects in the flawed object 
    system which we described earlier - you can’t have many of them, and if you 
    have more than a few hundred processes the system will start misbehaving and 
    to do any real work with them you have to write your own scheduler and start 
    combining multiple threads of control into single processes. All of this 
    gives concurrent programming a bad name - and would probably make any sane 
    person think that concurrent programming was a difficult and should be avoided 
    whenever possible. The opposite is true.
And:

    In Erlang processes are *light weight*. This means that very little 
    computational effort is required to create or destroy a processes. Light-weight 
    processes in Erlang are one to two order of magnitude lighter than operating 
    system threads.
    
    Not only are Erlang processes light-weight, but also we can create many 
    hundreds of thousands of such processes without noticeably degrading the 
    performance of the system (unless of course they are all doing something at the 
    same time).
In Go, "goroutines" are analogous to "processes" in Erlang in the above excerpt.

My point here was that Go solves the concurrency problem much differently than Java does, to a point where Go is much better suited to write concurrent programs than Java is. Joe Armstrong's argument in his paper applies pretty well here.

I'm not really sure what is to be gained by debating over whether Go was "intended" to be in the same domain as Java. I've used Go to solve problems that I might have otherwise solved in a variety of other languages (C, Haskell, Python). Had I ever been a Java programmer, I'm sure that would have been in the list too. Experience in speaking with other Go programmers leads me to believe that I am not unique in this regard.

[1] - "Concurrency oriented programming in Erlang", 2003. https://guug.de/veranstaltungen/ffg2003/papers/ffg2003-armst...

Re:Introduction to Go 1.1 by pron on Tuesday March 26, 2013 @08:56PM (#5447085)
Take a look at Akka actors. The JVM offers similar mechanisms, only with finer control over scheduling. But Go is fine and does have some advantages over the JVM (faster startup time) as well as disadvantages (dynamic code loading, runtime instrumentation, monitoring). Use it in good health!
Re:Introduction to Go 1.1 by tptacek on Tuesday March 26, 2013 @11:11PM (#5447589)
Isn't the "heaviness" of Go's threads due to do with how the thread stacks are allocated, not so much with how the threads are scheduled?
Re:Introduction to Go 1.1 by pron on Wednesday March 27, 2013 @06:02AM (#5448560)
In that case, Java allows for a very similar thing with fork-join. If you want to see exactly how, in two weeks I'll release an open-source library that wraps Java's fork-join as Go-like lightweight threads, only more preemptive and with better scheduling.