4 ms·

The problem is in enterprise Go is really hard to push currently due to management no having proper understanding of it. I believe Go is the future and I recent

by knodi 12y ago

The problem is in enterprise Go is really hard to push currently due to management no having proper understanding of it. I believe Go is the future and I recently tried to push Go in using it to write a new semi-real time system to handle many little messages with complex business logic but nope CTO went with node.js and have a callback hell. Sorry didn't mean to rant... Love Go its the future, use it.

0xdeadbeefbabe 12y ago
So why is node, with it's callback hell and single thread, worse? Is it syntax? That single thread assumption can free you from some significant problems, you know. golang's own http lib is event driven and uses callbacks, but perhaps less hellishly. I agree it is hard to push go if you don't properly understand it.
- frowaway001 12y ago
  Comparing Go and Node is like asking whether someone wants his paster served with vomit or feces. Yes, some people might prefer one over the another, but asking how they ended up with such a ridiculous issue would be a much better question.
- lebek 12y ago
  Go's http package doesn't use callbacks at the API level. See here http://golang.org/pkg/net/http/ http://golang.org/pkg/net/http/
codygman 12y ago
> I believe Go is the future and I recently tried to push Go in using it to write a new semi-real time system to handle many little messages with complex business logic but nope CTO went with node.js and have a callback hell. I used to think and hope Go was the future, and I agree it's better than node.js's callback hell, but I no longer hope Go is the future. Something like Nim[0] is an improvement in every way. Not my main point, but I personally moved from Go to Haskell. So, If you don't mind educating your developers Haskell, Scala, or Ocaml offers you true type safety and compile time correctness. 0: http://nim-lang.org/ http://nim-lang.org/
- AnimalMuppet 12y ago
  In this instance, I'm not sure that Haskell will help. If the GP couldn't get Go past the CTO, I strongly suspect that Haskell would also be vetoed.

by knodi 12y ago

0xdeadbeefbabe 12y ago

So why is node, with it's callback hell and single thread, worse? Is it syntax? That single thread assumption can free you from some significant problems, you know. golang's own http lib is event driven and uses callbacks, but perhaps less hellishly. I agree it is hard to push go if you don't properly understand it.

frowaway001 12y ago
Comparing Go and Node is like asking whether someone wants his paster served with vomit or feces. Yes, some people might prefer one over the another, but asking how they ended up with such a ridiculous issue would be a much better question.
lebek 12y ago
Go's http package doesn't use callbacks at the API level. See here http://golang.org/pkg/net/http/ http://golang.org/pkg/net/http/

codygman 12y ago

> I believe Go is the future and I recently tried to push Go in using it to write a new semi-real time system to handle many little messages with complex business logic but nope CTO went with node.js and have a callback hell. I used to think and hope Go was the future, and I agree it's better than node.js's callback hell, but I no longer hope Go is the future. Something like Nim[0] is an improvement in every way. Not my main point, but I personally moved from Go to Haskell. So, If you don't mind educating your developers Haskell, Scala, or Ocaml offers you true type safety and compile time correctness. 0: http://nim-lang.org/ http://nim-lang.org/

AnimalMuppet 12y ago
In this instance, I'm not sure that Haskell will help. If the GP couldn't get Go past the CTO, I strongly suspect that Haskell would also be vetoed.