News for hackers. Stuff that matters.
Re:Why we switched from Python to Go by BLanen on Tuesday October 17, 2017 @08:58PM (#15496174)
A thing that REALLY turned me off in go...

The fact that go's Math functions only work with floats. Idiotic.

You have so many packages that have to add the same freaking min(int a, int b) function.

Re:Why we switched from Python to Go by ahacker15 on Wednesday October 18, 2017 @08:29AM (#15498551)
Re:Why we switched from Python to Go by marcosdumay on Wednesday October 18, 2017 @10:36AM (#15499479)
So, one more vote for generics?
Re:Why we switched from Python to Go by tschellenbach on Tuesday October 17, 2017 @09:18PM (#15496236)
That is indeed quite weird
Re:Why we switched from Python to Go by ryanpepper on Wednesday October 18, 2017 @03:16AM (#15497460)
Does Go have templating?
Re:Why we switched from Python to Go by mmargerum on Wednesday October 18, 2017 @08:32AM (#15498570)
Templating is built right into the Stdlib https://golang.org/pkg/text/template/

The only 3rd party library I pull in to build web servers is gorilla (routing, sessions) and a database driver .

Everything else you need is in the go standard library .

Re:Why we switched from Python to Go by vgbm on Wednesday October 18, 2017 @11:18AM (#15499800)
I believe the parent means templating in the sense of generic types: https://en.wikipedia.org/wiki/Template_(C%2B%2B).
Re:Why we switched from Python to Go by closeparen on Wednesday October 18, 2017 @03:27AM (#15497499)
Nope! And that's most people's main problem with it.
Re:Why we switched from Python to Go by mmargerum on Wednesday October 18, 2017 @08:32AM (#15498571)
Wrong. Go has templating.
Re:Why we switched from Python to Go by baq on Wednesday October 18, 2017 @09:34AM (#15498963)
yeah, maybe, if what you want is to fill some strings in a template and not to create a type that's generic over other types.