The State of Go

Re:The State of Go by zak_mc_kracken on Saturday February 14, 2015 @10:48PM (#9051719)

It's not exactly the first the time Go team is showing that they haven't spent much time researching current practices, theory, research and tools in the field of software engineering.

Everything about the language screams of coming from minds who stopped learning new things in the late 90s.

[ Parent | on HN ]

Re:The State of Go by dsymonds on Saturday February 14, 2015 @11:15PM (#9051758)

I think you mean s/researching/adopting/, since you are only referring to the outcome, not the study or decision making that arrived at the outcome. The Go team generally knows about modern things; we deliberately choose not to use them when we don't think they suit Go.

[ Parent | on HN ]

Re:The State of Go by themightykevdog on Saturday February 14, 2015 @11:17PM (#9051764)

This is so colossally misguided a comment it's hard to know where to begin. So I won't.

[ Parent | on HN ]

Re:The State of Go by zak_mc_kracken on Saturday February 14, 2015 @11:28PM (#9051780)

See my comment about "not wanting to learn".

Happy to engage in a discussion about modern software engineering.

Are you?

[ Parent | on HN ]