Generics in Go with Ian Lance Taylor (2019)

Re:Generics in Go with Ian Lance Taylor (2019) by tptacek on Tuesday February 18, 2020 @08:04PM (#22362134)

The overwhelming majority of Go code isn't written at Google, and just a glance at Github will show you that it isn't being used to "jerk off into template engines" or "increase clickthrough rate by 0.1%". This comment contributes nothing to the discussion.

[ Parent | on HN ]

Re:Generics in Go with Ian Lance Taylor (2019) by monocasa on Tuesday February 18, 2020 @08:36PM (#22362329)

> The overwhelming majority of Go code isn't written at Google

I write go for my day job; I'm quite aware of their process. They control the language's future and new features pretty much single handedly. Also, I'd be very very surprised to find out that the overwhelming majority of code isn't written by google, do you have a stat on that you can quote?

> it isn't being used to"jerk off into template engines".

I'm saying go doesn't do that. You can't build these crazy compile time abstractions in it like you can other languages, and Google doesn't really need it to because they have enough man power to just brute force it. It doesn't want their workforce build abstractions for abstractions sake, and go doesn't really help you do that.

> or "increase clickthrough rate by 0.1%".

It is very much used to do that, I've been told by product and engineering friends at google.

[ Parent | on HN ]

Re:Generics in Go with Ian Lance Taylor (2019) by tptacek on Tuesday February 18, 2020 @09:08PM (#22362484)

I'm sure developers at Google use it to do that, because that is a problem that Google works on. It is not a problem that Cockroachdb works on, or that Docker works on, or that Hashicorp works on, or that Caddy works on, or that Tailscale works on.

[ Parent | on HN ]