4 ms·
Some see it as a compromising on types, I don't. After some years writing Scala code, trying to come up with even better types each day, Go to me is not a comp
by KingOfCoders 3y ago
Some see it as a compromising on types, I don't. After some years writing Scala code, trying to come up with even better types each day, Go to me is not a compromise but a relief.
My love for types peaked when I was in my mid-40s, now that I'm 50+ I want simple things.
- naasking 3y agoI'd call that disillusionment with bad type systems, which are indeed unnecessarily complex. We have yet to achieve a typing "nirvana", but we're getting closer IMO.
- margorczynski 3y agoFrom my experience this simplicity is something you pay the price along the way - development is harder (a good typing gives you a lot of hints about functionality and puts bounds on developers on how to use it) and more error prone (less stuff gets caught by the type checker, instead you find it out in runtime). Of course it is good to be reasonable - some people completely fly off into the FP world and instead of actually building working stuff they think all day about some clever abstraction and types to model it.
- pjmlp 3y agoI am almost 50, and my point of view on Go from 2012 has hardly changed. http://lambda-the-ultimate.org/node/4554#comment-71504 http://lambda-the-ultimate.org/node/4554#comment-71504 At least it does generics now.
- sigsev_251 3y ago> At least it does generics now Not in gccgo
- pjmlp 3y agoIndeed, as you see on other remarks from me I am aware of it, my point was about the language as designed, not the implementations ecosystem. TinyGo also doesn't do them.