News for hackers. Stuff that matters.

A comment on Go generics are not bad. Parent comment

Re:Go generics are not bad by margalabargala on Friday July 08, 2022 @07:01PM (#32028905)
Most things first exist, then exist and are good. We've seen the start of Go generics existing, but we haven't seen them be as good or as fast as they will ever be.

Five years from now, Go will still exist. The implementation of generics in that future version of Go is likely to be much faster and better than what we currently have.

Put a different way, "Generics are slow in Go v1.18"

[ Parent | on HN ]
Re:Go generics are not bad by humanwhosits on Friday July 08, 2022 @07:11PM (#32029040)
Someone will read a blog post about slow generics, ignore how it evolves, and tell every coworker for then next 10 years that go generics are slow
[ Parent | on HN ]
Re:Go generics are not bad by ascv on Friday July 08, 2022 @08:11PM (#32029816)
The authentic HN experience.
[ Parent | on HN ]
Re:Go generics are not bad by giancarlostoro on Friday July 08, 2022 @07:59PM (#32029684)
"Java is slow"
[ Parent | on HN ]
Re:Go generics are not bad by Rapzid on Friday July 08, 2022 @11:27PM (#32031287)
Not as slow as .Net !!
[ Parent | on HN ]
Re:Go generics are not bad by saagarjha on Friday July 08, 2022 @07:11PM (#32029041)
I'm hopeful, but the blog post doesn't say "Go generics have room to improve", it says "they're not bad". And they kind of are right now. I can see a road to how they can get better but it's not really very honest to present just this example as indicative of how they work.
[ Parent | on HN ]