4 ms·

maybe you should try it ... what about that? I bet you will change your mind. Both posts that you have linked are pretty much: "meh... i need s.th. to complain

maybe you should try it ... what about that? I bet you will change your mind. Both posts that you have linked are pretty much: "meh... i need s.th. to complain about"-posts. I've never been really affected by the issues they are screaming so loud about and believe me, I did not only write some toy projects [1] go is mega awesome and I love going back to the projects where I use it. It's a simple language that makes it very easy to write good code. And the library ecosystem is pretty good as well, especially when it comes to networking stuff. [1] https://github.com/MarkusPfundstein/taylor https://github.com/MarkusPfundstein/taylor

Varriount 6y ago
Note that they state "all things that have already been fixed". Did you use Go when these oversights were present?
- mpfundstein 6y ago
  So he complains about stuff that is alread fixed? Shall we now go back to the first version of ffmpeg? Or php pre php5? or pre java 8? or C++ pre C++11? Come on. He should try golang and then come back instead of relying on blogposts to form his opinion
  - Varriount 6y ago
    The argument being made is that Go's design isn't so much "forward thinking" as it is driven by Google's interests. What they are not stating is that Go is a conservative language with a standard library hampered by that conservatism, nor are they making a judgment on the current state of the language. If you are going to criticize someone's post, give them the respect of actually reading their argument, and not just writing a knee-jerk reaction.
- mratzloff 6y ago
  I did. Contrary a point above, I vendored dependencies in Go in 2012 the old school way: copy them into a vendor directory. It worked fine for end-user binaries, and you didn't have to worry about painfully long builds like you can get doing that with C++. The Go authors have explicitly stated they don't do things until they figure out the right way to do them. No language gets it all right out of the gate, but Go got pretty close with e.g. its standard library.

Varriount 6y ago

Note that they state "all things that have already been fixed". Did you use Go when these oversights were present?

mpfundstein 6y ago
So he complains about stuff that is alread fixed? Shall we now go back to the first version of ffmpeg? Or php pre php5? or pre java 8? or C++ pre C++11? Come on. He should try golang and then come back instead of relying on blogposts to form his opinion
- Varriount 6y ago
  The argument being made is that Go's design isn't so much "forward thinking" as it is driven by Google's interests. What they are not stating is that Go is a conservative language with a standard library hampered by that conservatism, nor are they making a judgment on the current state of the language. If you are going to criticize someone's post, give them the respect of actually reading their argument, and not just writing a knee-jerk reaction.
mratzloff 6y ago
I did. Contrary a point above, I vendored dependencies in Go in 2012 the old school way: copy them into a vendor directory. It worked fine for end-user binaries, and you didn't have to worry about painfully long builds like you can get doing that with C++. The Go authors have explicitly stated they don't do things until they figure out the right way to do them. No language gets it all right out of the gate, but Go got pretty close with e.g. its standard library.