News for hackers. Stuff that matters.
Re:Generics aren't ready for Go by throwaway415415 on Monday February 18, 2019 @09:45AM (#19190889)
Sucks for you, considered very good by plenty of other people who use it daily.
Re:Generics aren't ready for Go by rebeccaskinner on Monday February 18, 2019 @09:48AM (#19190929)
I use Go daily and I agree with the general sentiment that it's a janky language full of warts and could really benefit from features like generics.
Re:Generics aren't ready for Go by throwaway415415 on Monday February 18, 2019 @09:53AM (#19190973)
Maybe go back to java or c++? I'd rather have less people complain about a feature I don't want in the language.
Re:Generics aren't ready for Go by latronic_notron on Monday February 18, 2019 @10:51AM (#19191497)
Just curious: why don't you want generics in Go?

The language already uses them for Arrays, Maps and Slices, plus a lot of code relies on runtime-typed ad-hoc generics with interface{}.

It's not as if Go is a language without warts... there's a lot of ugly stuff, like Iota, Reflection, the error handling, interface{} itself.

This is a legitimate question, btw. Legitimately looking for other points of view

Re:Generics aren't ready for Go by apta on Monday February 18, 2019 @11:44AM (#19191942)
Keep in mind that many golang programmers just parrot what the golang authors say, without fully understanding it or even realizing the golang authors are wrong (not saying that's the case in this specific instance).

They hear the golang authors complain about Java, that it's the only way to do things, so they think that the only other solution is to go the extreme opposite way, not even looking at real modern languages (which golang isn't) like Kotlin or even C# for instance.

It's very evident that the golang authors have no experience designing language, and didn't look in depth at what other languages did.

Re:Generics aren't ready for Go by throwaway415415 on Monday February 18, 2019 @01:41PM (#19193017)
Unfortunately I am not parroting. If you are used to read code, and you read c++, you will see that templates are abused. No generics force devs to make their code clearer and thus more secure.

It is evident that Go is a better language than most thanks to the creators having deep experience in that domain.

Re:Generics aren't ready for Go by je42 on Monday February 18, 2019 @10:47PM (#19196436)
for sure i can abuse Go's language features as well in unintended ways.

Language abuse happens when the feature is the only available feature to implemented a particular and no other language feature allows for a better implementation.

in C++ most abuses of template are related to the missing feature "concepts". which took quite a while to get their.

If language switching is not an option, and your application requires generics and you are also required to use Go, you do have a problem. You need abuse the language and work around re-implement generics for Go.

Which can result in a very ugly development process, difficult to maintain code etc.

Re:Generics aren't ready for Go by latronic_notron on Monday February 18, 2019 @01:47PM (#19193095)
They aren't abused in C#, Java, Haskell, OCaml and other languages. Honestly, picking C++ as an example of traditional generic usage is a bit disingenuous.
Re:Generics aren't ready for Go by Gibbon1 on Monday February 18, 2019 @02:20PM (#19193415)
I think generics in C# are really well executed and solve a lot of problems in C#'s problem domain.

I do think you're on the right track that go's designers are pushing back hard on what they see as feature abuse in C++ and Java. C++ abuses templates and has dozens of ways to do anything that also don't interact with each other well. Java abuses inheritance, abstractions, and OOP.

go uses generics under the hood, probably the designers fear that generic's will also get abused if released into the wild. On the other hand I've never heard anyone bitch about well designed generics in other languages. Which is a tell since people will bitch about anything and everything.

Re:Generics aren't ready for Go by latronic_notron on Monday February 18, 2019 @02:24PM (#19193462)
> I do think you're on the right track that go's designers are pushing back hard on what they see as feature abuse in C++ and Java

Now that you mention it, I can't really blame them!

> On the other hand I've never heard anyone bitch about well designed generics in other languages. Which is a tell since people will bitch about anything and everything.

That's my opinion as well. Generics are quite pleasant, simple and a great tool to have when they're well designed.

Re:Generics aren't ready for Go by spion on Monday February 18, 2019 @02:14PM (#19193363)
I would suggest a Go programmer give ReasonML an honest try (as an example language where "generics" are done right), but the getting started / documentation situation is still not at Golang level so thats a bit annoying.

Maybe F# would be a better choice. .NET Core and its tooling are pretty well done. C# and NET Core would be another nice alternative.

Re:Generics aren't ready for Go by latronic_notron on Monday February 18, 2019 @02:25PM (#19193480)
Agreed. I find C# and F# surprisingly refreshing. ReasonML is a bit unfinished, but it's a sign of great things to come.
Re:Generics aren't ready for Go by apta on Monday February 18, 2019 @03:58PM (#19194376)
golang authors seem to only have experience with C++ as they keep talking about C++'s deficiencies, as if it's the only other language that exists when it comes to generics.
Re:Generics aren't ready for Go by throwaway415415 on Monday February 18, 2019 @04:49PM (#19194791)
Sure. Seems like they have the same experience than me then.
Re:Generics aren't ready for Go by apta on Tuesday February 19, 2019 @12:40PM (#19200930)
The point is that they are not familiar with the solutions other languages have. So it's either the C++ way or don't look elsewhere.
Re:Generics aren't ready for Go by throwaway415415 on Monday February 18, 2019 @01:39PM (#19193004)
Because they are easily abused (look at c++) and makes code unreadable. Working around generics usually make the code clearer and thus more secure
Re:Generics aren't ready for Go by latronic_notron on Monday February 18, 2019 @01:45PM (#19193076)
Go has interface{}, which can be abused as much as generics for the same purpose, but without the type safety, hence, less secure.

And nobody is advocating C++ style template metaprogramming. There are much better implementations of generics, as acknowledged by Russ Cox himself.

Re:Generics aren't ready for Go by throwaway415415 on Monday February 18, 2019 @04:50PM (#19194805)
Usually interface{} is abused by java programmers. I agree that it's not great, but if you don't come from java or c++ chances you won't follow these patterns at least.
Re:Generics aren't ready for Go by rebeccaskinner on Monday February 18, 2019 @10:24AM (#19191271)
I'd love to get away from Go again, but unfortunately it's the hot thing that people see on your resume and then they don't want to talk to you about anything else. I'm very concerned that in a few years it's going to be the terrible low-paying boring thing that people see on your resume and don't want to talk to you about anything else.
Re:Generics aren't ready for Go by throwaway415415 on Monday February 18, 2019 @01:39PM (#19192997)
Its the hot thing for a reason. Adapt or be left out.
Re:Generics aren't ready for Go by rebeccaskinner on Monday February 18, 2019 @08:27PM (#19195998)
I've been using Go in production for 5 years now, I don't think there's a lot of adapting left to do. From the other side of a few years of experience I think I see the reality of the situation pretty clearly. Go isn't a good language by any means. It's the hot thing because it's a marginally less painful blub than python or java and cheap entry-level developers can be onboarded to it quickly and be left to churn out boring but largely unharmful code. On top of it's programming with mittens mentality it had the force multiplier effect of becoming the devops language dejure. I think the staying power of Go is largely dependent on whether or not the industry finds the current state of devops a local maxima that it sticks on for a while, or whether things push further into PaaS territory and the current devops tooling becomes irrelevant for everyone except the big cloud platform implementers.
Re:Generics aren't ready for Go by kasey_junk on Monday February 18, 2019 @09:50AM (#19190943)
Same
Re:Generics aren't ready for Go by spion on Monday February 18, 2019 @12:15PM (#19192206)
There are plenty of people who consider C++ good too and its used by people daily. Doesn't mean that Rust isn't a better language, even though there are less people that use it daily.

I think we need to be real about what are the strengths and weaknesses of each platform instead of drinking the coolaid. Otherwise we don't learn anything and the bad parts are going to find their way in the next one.