5 ms·
Its as been a research project for a very very very long time now ...
by babawere 13y ago
Its as been a research project for a very very very long time now ...
- otterley 13y agoIt took Java over 8 years to get generics. Be patient. :)
- coldtea 13y agoYes, because it sure worked well for Java, this slowness...
- enneff 13y agoYeah, we've been busy making the language, libraries, and tools great. Sorry about that.
- jlmendezbonini 13y agoPlease ignore him/her. There are a lot of us who are very excited about the work the Go team is doing.
- coldtea 13y agoSo instead of "research project", a better description would be "very low on the list of priorities, nobody cares about it"?
- enneff 13y agoNo. People continue to work on it. A lot of time has been spent on it. I really don't appreciate your mischaracterization.
- coldtea 13y agoWell, I'm sorry, but I haven't seen this from following Go from a (small) distance -- and doing some work projects with it. Perhaps those people working on it can give an update or some info on their work? Even a "we tried this approach, it's too cumbersome so we abandoned it" or "we pursue this idea, but we're still ways off" etc, would suffice.
- overcyn 13y agoAren't you just kinda being a dick here? A go developer has directly responded to you multiple times, saying that this is a topic that they're actively researching. And you just keep replying with skepticism asking for actual proof. No one owes you anything here. I hope you don't behave this way with other open source projects.
- frowaway001 13y agoNo, but he has all the right to question their claims of "doing all the research in secret" and call them bullshit if he wants. Anyway, just consider what their behavior says about how they think of their users.
- overcyn 13y agoHe has all the right to say whatever he wants and believe whatever he wants. Doesn't mean he should be rude.
- Dylan16807 13y agoAsking for a status blog post once every couple years is not rude.
- coldtea 13y ago>And you just keep replying with skepticism asking for actual proof. Should I just accept the same kind of answer we've had for 4 years on the Go webpage, and move on? You talk about wanting "actual proof" as if it's a bad thing. Where's the harm in wanting "actual proof"? Did Ken Ham proved it overrated? Notice how the top voted comment in this thread, showing a clear community interest, makes the same point: "I'm surprised at the lack of progress in generics for Go. But more than progress, I'm surprised at the lack of a story about generics in Go. Yes, the FAQ waves its hands at complexity, but the lack of discussion and/or proposals puzzle me." >No one owes you anything here. That doesn't preclude discussion, having questions and, yes, even doubting overly generic answers. Noone owes anything to the Python community either, but they are far more open with such things. Perhaps I want to know if Go wants to be a real community project, or a "developed by a core team at Google in secrecy you get what we want you to get when we want you to get it" thing.