News for hackers. Stuff that matters.
Re:The State of Go by rpercy on Sunday February 05, 2017 @10:36AM (#13572769)
To each their own. I enjoy writing Go almost as much as writing Python. But more importantly I find reading Go easier than any other language - mostly due to its explicitness and consistency between authors. That has made it much easier to dig into code bases that solve some very complex and interesting (to me, anyway) problems.

Also, I assume the 'no type safety' statement is just hyperbole?

Re:The State of Go by bitexploder on Sunday February 05, 2017 @12:29PM (#13573385)
They probably mean you can use interface{} and create a typing black hole if you really wanted to. Otherwise, I don't know.
Re:The State of Go by kuschku on Sunday February 05, 2017 @02:21PM (#13574016)
Or maybe they mean that you HAVE to use interface{} for any reasonable kind of generics, such as developing generic data structures, or generic handlers for RPC interfaces allowing arbitrary nesting?

Even the stdlib uses interface{} everywhere now: https://tip.golang.org/pkg/sort/#Slice

Re:The State of Go by bitexploder on Sunday February 05, 2017 @07:31PM (#13575630)
Is a good point. Smells of void pointers and old school Java collections.