News for hackers. Stuff that matters.
Re:Why Go Is Not Good (2014) by gendoikari on Wednesday December 09, 2015 @10:55AM (#10704331)
Mmmm I'm puzzled. I don't think we are consulting the same community... Goroutines are everywhere in all the main go projects. Goroutines and channels are one of the main reasons Go exists.
Re:Why Go Is Not Good (2014) by mike_hearn on Wednesday December 09, 2015 @12:21PM (#10705067)
"Readability reviews" at Google are somewhat notorious for imposing fairly arbitrary style choices extremely rigidly, for instance 80 characters per line (woe betide you if even one line in a 5000 line patch is 81 characters...). It doesn't sound so surprising to me that the people behind such a process might have decided that one of Go's primary selling points is 'confusing', given that the Go authors appear to believe their colleagues can't handle a brilliant language!
Re:Why Go Is Not Good (2014) by cmrdporcupine on Wednesday December 09, 2015 @10:59AM (#10704388)
It's quite possible. After my experience with Go code reviews internally at Google, though, I am not eager to go back. I'd work on a project if I was paid to do it, but I wouldn't start one or advocate for it.
Re:Why Go Is Not Good (2014) by kungfooguru on Wednesday December 09, 2015 @12:22PM (#10705081)
He said at Google not the community. I wouldn't doubt there is a difference.
Re:Why Go Is Not Good (2014) by gendoikari on Wednesday December 09, 2015 @02:37PM (#10706146)
I'm pretty sure at Google they know why they created Go, why they're using Go, and so on... The assumption that Google reviewers had something against goroutine puzzles me a bit. Maybe the problem was not about goroutines, but about how they were used... I don't know, I'm guessing...