[dead]
Re:Go generics proposal moves to “likely accept”
by jacques_chester on Wednesday February 03, 2021 @05:22PM
(#26019961)
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.
Re:Go generics proposal moves to “likely accept”
by bcrosby95 on Wednesday February 03, 2021 @05:34PM
(#26020098)
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.
Re:Go generics proposal moves to “likely accept”
by jacques_chester on Wednesday February 03, 2021 @06:06PM
(#26020447)
> 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.
Re:Go generics proposal moves to “likely accept”
by jklehm on Wednesday February 03, 2021 @08:22PM
(#26021458)
> no final nirvana language.
There isn't one...yet!
Re:Go generics proposal moves to “likely accept”
by bobthebuilders on Wednesday February 03, 2021 @04:54PM
(#26019666)
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.
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.