<- Back
Comments (164)
- DarkNova6Step by step, Go is now learning the hard lessons every other language has learned over the last 20 years. The fact that despite their best efforts, their propositions look like everone else is a surprisingly refreshing affirmation of status quo.
- nasretdinovWell, better late than never. Stuff like sets or a typed heap is long overdue. Maybe they'll even add iterator API for database/sql results this decade too (something like my pull request for sqlx https://github.com/jmoiron/sqlx/pull/990 but maybe more polished)
- vander_elstI find it so sad that people wasted millions of hours and lines of code rewriting over and over basic constructs that should have been on the language in the first place. How many years before we finally get sum types?
- dgunayIt's cool that they're doing this but with iterators and soon in 1.27 generic method parameters, you can already DIY most of this with little effort. I've got iterators at work for nearly everything I could want, small libraries for extra mapping, filtering etc operations, and with agents going back and actually refactoring old code to use them is easier than ever.
- kamma4434Welcome to Java, where Collections are the bread and butter of every programmer since 1998.While you are at it, I humbly suggest to add composable streams too, that we had in 2014, and that make working with collections way more pleasant.(Jokes aside, in Java it is very nice that you can start with a generic ArrayList and turn it into a linked list with one single keyword change and no code needs changing, or that you can turn any collection into a synchtonized or readonly doppelganger with one line of code. Collections are nice and I miss them in Golang)
- jiehongWell, finally!I wish they wouldn’t mix mutation methods in there, but ok.
- athoraxOn one hand I'm glad to see this being added, but its becoming obvious building generics into the language as-is just isn't a good fit. Hopefully Go v2 can solve this at a more foundational level while still allowing interop or easy porting form current go code.
- improgrammer007First they said they won't add generics. They violently defended that decision. Developers bent over backwards to make it work without generics. Some even wrote long blog posts defending Rob Pike's decision. Some wrote posts arguing against it. Now the Golang team adds them. Why waste so much developer time? It's not a few months. It's several years. This industry is seriously a clown show tbh.
- valcron100022 years late, but better late than never.
- troupoGo is rediscovering Guy Steele's Growing a Language from first principles, at a much slower pace: https://youtu.be/_ahvzDzKdB0?is=qZdfiT3792XyHxSJ
- alfiedotwtfNo reference to Canadian Aboriginal characters in the comments :(
- anonundefined
- akiarieHonestly the more I see this the less I like Golang. Generics was the worst thing ever added to the language. We're making it easier for library builders and harder for ordinary code to be written.
- roundwegoA bit too late frankly. The snobbish arrogance didn’t help.
- shevy-javaGolang's biggest problem is a certain company.
- znpyLooking forward to see G2EE being released as a specification /s
- pifPeople still calling themselves developers and choosing a language that was created for poor programmers...