3 ms·

It depends on how you define "need". Golang could be replaced with a notation for NAND gates and still be able to "do" everything it does now. Yesterday I was

It depends on how you define "need". Golang could be replaced with a notation for NAND gates and still be able to "do" everything it does now. Yesterday I was in a pairing interview where I debugged and sped up some code. All-in-all I wound up with about 200 lines or so of Golang, including a lot of "yes, another loop" code. All I was doing, really, was mapping, forking and joining. Meanwhile in Java, I could have gotten most of this in about 20 lines withJava 8 Streams and .parallel(). Generics make that tractable.

geodel 6y ago
Strange. Why you keep torturing yourself with Go? Wouldn't just moving (or just staying?) on Java save you lot of grief. On the other hand a non-technical employer might force employees to new/fashionable things, so that could be the case.
- bobthebuilders 6y ago
  Perhaps their existing codebase is in Go and they need to use a utility. Perhaps they really like the performance of Go compared to Java. Perhaps they can't just use Java because of inertia or that no one else knows Java. Languages have warts, and wanting to remove one is not a bad idea.
- jacques_chester 6y ago
  No, I had chosen Go for that problem. My reasoning was that most of the code I've read or written in the past 2 years has been Go, so it seemed like I should focus on using a language where I was warmest. But in retrospect I would have preferred Java. That's my fault.
  - bcrosby95 6y ago
    If you did, I wonder if you would regret choosing Java over Go for other reasons. I tend to find that no matter what language I choose, there's some parts of the code that I would prefer to be able to write in a different language.
    - jacques_chester 6y ago
      > I tend to find that no matter what language I choose, there's some parts of the code that I would prefer to be able to write in a different language. There is no final nirvana language. That is the awful truth of existence.
      - jklehm 6y ago
        > no final nirvana language. There isn't one...yet!

geodel 6y ago

Strange. Why you keep torturing yourself with Go? Wouldn't just moving (or just staying?) on Java save you lot of grief. On the other hand a non-technical employer might force employees to new/fashionable things, so that could be the case.

bobthebuilders 6y ago
Perhaps their existing codebase is in Go and they need to use a utility. Perhaps they really like the performance of Go compared to Java. Perhaps they can't just use Java because of inertia or that no one else knows Java. Languages have warts, and wanting to remove one is not a bad idea.
jacques_chester 6y ago
No, I had chosen Go for that problem. My reasoning was that most of the code I've read or written in the past 2 years has been Go, so it seemed like I should focus on using a language where I was warmest. But in retrospect I would have preferred Java. That's my fault.
- bcrosby95 6y ago
  If you did, I wonder if you would regret choosing Java over Go for other reasons. I tend to find that no matter what language I choose, there's some parts of the code that I would prefer to be able to write in a different language.
  - jacques_chester 6y ago
    > I tend to find that no matter what language I choose, there's some parts of the code that I would prefer to be able to write in a different language. There is no final nirvana language. That is the awful truth of existence.
    - jklehm 6y ago
      > no final nirvana language. There isn't one...yet!