I had different opinion than guy who joined the Go team in 2019 (Ian Lance Taylor). I was banned from their github repo, my AdSense sites were removed from Google's index, my AdSense CPC dropped by 2/3. My github account was "flagged" aka disabled from being seen in public. I was on github for 7 years. I received nonsensical "not in accordance to policies" messages from AdSense all of a sudden when that happened aka…
Eleven Years of Go
11–20 of 170 posts
Re: Eleven Years of Go
#12Earlier quoted context omitted.
I've not had a good experience with them either. I was contributed a bug fix to the std lib which would've been a decent feather in my cap. Not even a thanks; some maintainer copied, pasted, made a few changes, merged "his" fix. 2014 iirc; extinguished my interest.
Any commits we can refer to, so we can expose this situation for potential contributors?
Re: Eleven Years of Go
#13I had different opinion than guy who joined the Go team in 2019 (Ian Lance Taylor). I was banned from their github repo, my AdSense sites were removed from Google's index, my AdSense CPC dropped by 2/3. My github account was "flagged" aka disabled from being seen in public. I was on github for 7 years. I received nonsensical "not in accordance to policies" messages from AdSense all of a sudden when that happened aka…
I just want to note one thing: any large community will have aspect (sometimes many) that many people will not like. That's not personal, it's just statistics. And when someone (Go team, Stack overflow a few years back, ...) appears heavy-handed, try to imagine to herd hundred-thousand creative, intelligent spirits - that's an impossible task. If you complain about the font (and others did, too) than either ask yourself, whether the stress of conflict is worth it - or leave the matter - or the community - for good.
Re: Eleven Years of Go
#14The template declaration and invocation hierarchy seems unnecessarily complex and is almost 100% undocumented. It just hurts my brain and doesn't make any sense to me in comparison to jinja, whatever jekyll uses, etc.
It has very very poor documentation. Some docstrings are not a replacement for actual documentation when your approach is that unorthodox.
And it doesn't produce any error messages or warnings when you do something wrong - just renders a completely blank template.
EDIT: to be clear, my beef is with the template hierarchy, poor docs, and lack of errors/warnings, not with the general capabilities of the library, which are quite complete.
Re: Eleven Years of Go
#15I had different opinion than guy who joined the Go team in 2019 (Ian Lance Taylor). I was banned from their github repo, my AdSense sites were removed from Google's index, my AdSense CPC dropped by 2/3. My github account was "flagged" aka disabled from being seen in public. I was on github for 7 years. I received nonsensical "not in accordance to policies" messages from AdSense all of a sudden when that happened aka…
I'm pretty sure that Ian has been part of the Go team since before the public release in 2009. He's the most patient person I have ever seen in my entire life.
edit: He joined mid 2008 https://www.youtube.com/watch?v=LqKOY_pH8u0&t=1m19s
Re: Eleven Years of Go
#16I had different opinion than guy who joined the Go team in 2019 (Ian Lance Taylor). I was banned from their github repo, my AdSense sites were removed from Google's index, my AdSense CPC dropped by 2/3. My github account was "flagged" aka disabled from being seen in public. I was on github for 7 years. I received nonsensical "not in accordance to policies" messages from AdSense all of a sudden when that happened aka…
Re: Eleven Years of Go
#17Re: Eleven Years of Go
#18I have really been enjoying Go, except for the built-in templating library. It's a wart on the standard library IMO. The template declaration and invocation hierarchy seems unnecessarily complex and is almost 100% undocumented. It just hurts my brain and doesn't make any sense to me in comparison to jinja, whatever jekyll uses, etc. It has very very poor documentation. Some docstrings are not a replacement for actual…
Re: Eleven Years of Go
#19Generics Update: "We will be working on that throughout 2021, with a goal of having something for people to try out by the end of the year, perhaps a part of the Go 1.18 betas."