News for hackers. Stuff that matters.
Re:Rust via its Core Values by vardump on Sunday April 03, 2016 @05:09PM (#11417749)
So please tell us what is a productive language?

At least any argument why Go is not productive, why its productivity is an illusion.

Re:Rust via its Core Values by pjmlp on Monday April 04, 2016 @01:04AM (#11419547)
> At least any argument why Go is not productive, why its productivity is an illusion.

- generic code only via go generate and interface {}

- verbose error handling

- the way dependencies are handled

- no language support for functional paradigms

- nil pointer semantics in interfaces

- very thin type system

Go would be a great language in the mid-90's, nowadays given the features adopted in the mainstream it feels too little.

For me, the positive thing is that it may lure developers that would use C to use Go instead, and in the process discover that their use case is perfectly doable with a memory safe language.

Re:Rust via its Core Values by vardump on Monday April 04, 2016 @04:59AM (#11420333)
I've done one successful small/medium size TCP server project in Golang. Primarily programming in C++.

- Generics were absolutely no issue. - Golang error handling may be verbose, but it also ensures errors locally visible and are handled where they occur. Just need to ensure all return values are handled. I much prefer it to C++, where you can never tell from local context what might throw and what won't.

Generally I found it to be very productive compared to at least C++ and Java.

Two aspects of Golang were a huge productivity boost for the project in question: struct automatic (de)serialization to JSON, XML, etc. was very nice. Goroutines and channels simplified the code.