News for hackers. Stuff that matters.
Re:D for the Win by cjslep on Friday August 22, 2014 @08:22AM (#8211750)
> go (Google must be joking if they actually consider it for system programming)

I am curious what led the author to be dismissive of Go in such a strongly negative manner. Lack of generics? Disagree with certain language design choices? Too many cuddly caricatures of gophers?

Re:D for the Win by agumonkey on Friday August 22, 2014 @08:33AM (#8211787)
I need some clarifications. I think there are two definitions of systems being used here :

  - low-level hardware control (c,D,...) implicitely concurrent
  - explicitely concurrent higher level components (go, erlang maybe)
Re:D for the Win by tomwilde on Friday August 22, 2014 @08:35AM (#8211796)
Hail Wikipedia for it is the source of all truth.

http://en.wikipedia.org/wiki/System_programming_language

Re:D for the Win by agumonkey on Friday August 22, 2014 @08:47AM (#8211831)
C and Go both classified as high level system language, but I can't deny the fact that C allows for finer control over machine usage so it's hard to put Go in the same bag.
Re:D for the Win by tomwilde on Friday August 22, 2014 @09:27AM (#8211969)
You are right yet Go is much closer to C than Erlang in syntax, type system and memory-representation. Go is so close to C in fact, that its compiler is a modified C compiler.

Therefore I'd bundle it with C and D rather than Erlang.

Re:D for the Win by voidlogic on Friday August 22, 2014 @11:59AM (#8212642)
I think of Go as "C++", but as brought to you by the guys who made C, with tasty sprinkles from CSP and Python.
Re:D for the Win by coldtea on Friday August 22, 2014 @08:43PM (#8214588)
It's mostly Java from the people who made C, but didn't learn much from their C design mistakes.
Re:D for the Win by voidlogic on Sunday August 24, 2014 @12:19AM (#8217673)
Ridiculous. Go's lack of verbose classes and lack of inheritance, pass everything by value, the existence of pointers, first class concurrency primitives, compile to binary / no interpretation/JIT, lack of a VM, built in unit testing/benching, fast compile times, memory usage, easy C integration, etc etc all make it very different from Java.

I've been writing Go full-time for over 2 years and used to write mostly Java/C#, so I should know. When I started with Go and ported many of my personal Java applications, they all were much more maintainable and straight forward in Go.

Of course C had always been favorite language, and all I ever really wanted was a "modern" C, so I am probably biased.

Re:D for the Win by agumonkey on Friday August 22, 2014 @09:57AM (#8212087)
Agreed, I meant Erlang for its use. It's hard to be more different than Erlang in implementation :)
Re:D for the Win by codygman on Friday August 22, 2014 @09:00AM (#8211884)
I think "erlang definitely" is more accurate. That's is erlang's domain and it does it better than any other solutions right now AFAIK.
Re:D for the Win by agumonkey on Friday August 22, 2014 @09:10AM (#8211908)
So Go 'system' is the cybernetics/communication one.
Re:D for the Win by Ironballs on Friday August 22, 2014 @08:24AM (#8211760)
Go hasn't been intended for "systems programming" for quite a while. It is a general purpose language.
Re:D for the Win by tomwilde on Friday August 22, 2014 @08:33AM (#8211789)
Those properties are not mutually exclusive.
Re:D for the Win by seabee on Friday August 22, 2014 @08:57AM (#8211874)
C++ is the counterexample in nearly all such cases, for better or worse!
Re:D for the Win by rakoo on Friday August 22, 2014 @12:15PM (#8212722)
The important distinction here is that go creators never set "system programming" as a goal, contrary to what OP implied in the blog post.

Now, whether go turns out to be good at that task is another story

Re:D for the Win by andralex on Friday August 22, 2014 @02:19PM (#8213268)
Go has been announced as a systems programming language: https://www.youtube.com/watch?v=rKnDgT73v8s. After some backlash the slogan has been changed quietly.
Re:D for the Win by jacques_chester on Friday August 22, 2014 @08:43AM (#8211817)
Nevertheless, many of the design decisions make sense in that context.

For example: the difference in initialisation of simple data types vs slices and maps. For an application programmer these are weird inconsistencies. But they make sense in the domain.

Or the way error handling works. Very tedious to have to do-check, do-check, and not be able to have automatic upwards delegation. But in system programming it's about robustness, not ease of development. A database server can't just restart if it has a file or memory problem. There needs to be a solution and it needs to be immediately next to the problem.

Re:D for the Win by Gracana on Friday August 22, 2014 @11:04AM (#8212399)
I don't do anything quite so tedious in my Go-based webserver projects. For functions that can return errors that I don't have a way to recover from (db calls, for example), I use a simple rapper function that automatically logs errors and panics. That doesn't seem to me like much of a source of difficulty or complexity.
Re:D for the Win by jacques_chester on Saturday August 23, 2014 @10:49AM (#8215926)
Web apps are apps, they have different expectations and provide different levels of robustness guarantees. As I said, Go's design decisions are motivated by a different problem domain.

That being said, I've followed a similar pattern in writing Go web apps. I passed errors upwards from their originating site to the HTTP handler functions, because that was where the error handling was possible with the best context.