News for hackers. Stuff that matters.

A comment on Twelve Go Best Practices. Parent comment

Re:Twelve Go Best Practices by dscrd on Wednesday July 31, 2013 @12:10PM (#6134774)
They allow dynamically typed methods when you need them. Why does that make you sad?
[ Parent | on HN ]
Re:Twelve Go Best Practices by nine_k on Wednesday July 31, 2013 @02:41PM (#6135941)
Loss of strong typing and runtime type detection is what makes me sad.

Well, Go 1 has some of the problems of Java 1: no generics, typecasts from interface{} here and there, simplistic GC. Reasons are probably similar: this all is good enough for version 1, and can later be improved upon.

[ Parent | on HN ]
Re:Twelve Go Best Practices by kristianp on Wednesday July 31, 2013 @09:24PM (#6138030)
"Well, Go 1 has some of the problems of Java 1: no generics, typecasts from interface{} here and there, simplistic GC. Reasons are probably similar: this all is good enough for version 1, and can later be improved upon."

Except I doubt we're going to see generics in Go version 2, whenever that may be. The sentiment against it has been pretty strong in the golang-nuts mailing list.

[ Parent | on HN ]