Show HN: My notes on Working with Go
github.com
Show HN: My notes on Working with Go
1–10 of 91 posts
Re: Show HN: My notes on Working with Go
#2Re: Show HN: My notes on Working with Go
#3It's just code with comments what code is doing. Can we call them notes?
Re: Show HN: My notes on Working with Go
#4Re: Show HN: My notes on Working with Go
#5Note nº 1: don't!
Re: Show HN: My notes on Working with Go
#6Note nº 1: don't!
Care to elaborate?
Re: Show HN: My notes on Working with Go
#7Earlier quoted context omitted.
Care to elaborate?
It ignores some historical bad design decisions, the worst of them being having null in the language, the famous one billion dollar mistake. And well, no support for functional/immutable data structures is something I dislike. My squad did a micro-service in Go at work and was not pleasant as we expected.
Re: Show HN: My notes on Working with Go
#8It's just code with comments what code is doing. Can we call them notes?
Re: Show HN: My notes on Working with Go
#9It's just code with comments what code is doing. Can we call them notes?
would be useful to somebody, seems like a good idea to me.
Re: Show HN: My notes on Working with Go
#10Earlier quoted context omitted.
It ignores some historical bad design decisions, the worst of them being having null in the language, the famous one billion dollar mistake. And well, no support for functional/immutable data structures is something I dislike. My squad did a micro-service in Go at work and was not pleasant as we expected.
what language do you suggest instead of go?