News for hackers. Stuff that matters.
Re:Go 1.8 Release Notes by wyager on Thursday February 16, 2017 @02:53PM (#13663005)
> They are just types and they are here to help the developer write compile time type safe code.

Type safety mostly appeals to developers with a low time preference. Getting a bunch of compiler errors is the opposite of immediate gratification. In a language like python, you can start running your program instantly and push dealing with bugs as far back as possible. You might spend more time, since debugging is harder and slower in the long run than making the compiler catch mistakes up front, but you get to procrastinate.

Re:Go 1.8 Release Notes by dpc_pw on Friday February 17, 2017 @03:25AM (#13666784)
> In a language like python, you can start running your program instantly and push dealing with bugs as far back as possible.

Which is often never. Part of the reason why I avoid using anything written in Python.

Re:Go 1.8 Release Notes by junk_disposal on Thursday February 16, 2017 @03:25PM (#13663265)
1. Sometimes being able to ship is more important than being perfect 2. Sometimes I don't care if it's perfect. If I need something for in-house use, Go (and Python) is quite enough for my needs.