5 ms·

Not only is this page riddled with typos that lead me to doubt the quality of the code, the concept of a framework is fundamentally complex and at odds with the

by stirner 10y ago

Not only is this page riddled with typos that lead me to doubt the quality of the code, the concept of a framework is fundamentally complex and at odds with the goals of Go.

lucasp82 10y ago
The project creator is from Greece and is not a native English speaker. How about maybe cut some slack.
- stcredzero 10y ago
  Sure, so long as he's open to incorporating corrections.
zongitsrinzler 10y ago
Because being a native english speaker has a lot to do with the quality of code, how rude..
- tumdum_ 10y ago
  Typos are easily checked by dictionary - no need to be native speaker for that :)
  - Etheryte 10y ago
    Checking for typos using a dictionary makes little sense. Let's take the example that was pointed out in another comment: "It’s gonna work good on all devices." According to a dictionary (Oxford American, but use which ever you prefer), good can for example stand for "having the required qualities, of a high standard", which can easily sound fitting when you're not a native speaker.
- stirner 10y ago
  English is a language with grammar that has a Stack Exchange site and can be Googled. The typos on the page are common for native English speakers who don't take the time or effort to check their writing for correctness. The author did not grow up from babyhood writing Go programs, but we expect them to be correct and adhere to known idioms.
  - Etheryte 10y ago
    The same can, for example, be said about Russian, but I doubt you would expect anyone with minimal experience in Russian to write without any errors despite that fact.
    - stcredzero 10y ago
      Being a learner is laudable. However, that means being open to constructive criticism.
spriggan3 10y ago
> Not only is this page riddled with typos I'd argue that at least the author tried to write a real documentation, which 95% of Go library authors don't do. > the concept of a framework is fundamentally complex and at odds with the goals of Go The famous "You don't need that with Go ™ ". It's more like Gophers hate the word "framework","dependency injection" and "orm". It's hardly a framework, it's a router and a middleware stack. Instead of being enthusiastic about others using their language, like in any other community, Gophers like to hate, shame, mock other people because they didn't do things "the Go way", whatever they think it is. It's one of the most toxic community I have ever seen.
- marcus_holmes 10y ago
  I enjoyed coding in Go, but the "community" killed all enjoyment of the language for me. I took off my big boy trousers, put on my human being shorts, and decided to take my enthusiasm elsewhere. Shame, because the language does have a lot going for it.
- stirner 10y ago
  I didn't mean to hate, shame, or mock anyone. I would rather that programmers who create complex antipatterns stay in other languages that encourage them, and if light critique has that side effect, so be it.
  - codezero 10y ago
    I'm sure the author would love your help fixing up the typos: https://github.com/iris-contrib/website https://github.com/iris-contrib/website I just submitted a PR to fix a few minor issues. In general, the grammar issues here are really minimal and the page seems to communicate the project and its goals very clearly without being too distracting. I didn't find any explicit typos, like misspelled words, but I didn't look that hard either, hopefully you can help out!
    - stirner 10y ago
      Really, the typo thing was not the main point of my original comment, it was just an aside. I'm sorry to anyone I have offended. I mainly take issue with the proliferation of Go frameworks, especially HTTP frameworks. Frameworks are an antipattern and there are already a huge number of HTTP frameworks that are all incompatible and reimplement the same functionality. I don't think this is useful for the language and in fact think it hurts it.

by stirner 10y ago

Not only is this page riddled with typos that lead me to doubt the quality of the code, the concept of a framework is fundamentally complex and at odds with the goals of Go.

lucasp82 10y ago

The project creator is from Greece and is not a native English speaker. How about maybe cut some slack.

stcredzero 10y ago
Sure, so long as he's open to incorporating corrections.

zongitsrinzler 10y ago

Because being a native english speaker has a lot to do with the quality of code, how rude..

tumdum_ 10y ago
Typos are easily checked by dictionary - no need to be native speaker for that :)
- Etheryte 10y ago
  Checking for typos using a dictionary makes little sense. Let's take the example that was pointed out in another comment: "It’s gonna work good on all devices." According to a dictionary (Oxford American, but use which ever you prefer), good can for example stand for "having the required qualities, of a high standard", which can easily sound fitting when you're not a native speaker.
stirner 10y ago
English is a language with grammar that has a Stack Exchange site and can be Googled. The typos on the page are common for native English speakers who don't take the time or effort to check their writing for correctness. The author did not grow up from babyhood writing Go programs, but we expect them to be correct and adhere to known idioms.
- Etheryte 10y ago
  The same can, for example, be said about Russian, but I doubt you would expect anyone with minimal experience in Russian to write without any errors despite that fact.
  - stcredzero 10y ago
    Being a learner is laudable. However, that means being open to constructive criticism.

spriggan3 10y ago

> Not only is this page riddled with typos I'd argue that at least the author tried to write a real documentation, which 95% of Go library authors don't do. > the concept of a framework is fundamentally complex and at odds with the goals of Go The famous "You don't need that with Go ™ ". It's more like Gophers hate the word "framework","dependency injection" and "orm". It's hardly a framework, it's a router and a middleware stack. Instead of being enthusiastic about others using their language, like in any other community, Gophers like to hate, shame, mock other people because they didn't do things "the Go way", whatever they think it is. It's one of the most toxic community I have ever seen.

marcus_holmes 10y ago
I enjoyed coding in Go, but the "community" killed all enjoyment of the language for me. I took off my big boy trousers, put on my human being shorts, and decided to take my enthusiasm elsewhere. Shame, because the language does have a lot going for it.
stirner 10y ago
I didn't mean to hate, shame, or mock anyone. I would rather that programmers who create complex antipatterns stay in other languages that encourage them, and if light critique has that side effect, so be it.
- codezero 10y ago
  I'm sure the author would love your help fixing up the typos: https://github.com/iris-contrib/website https://github.com/iris-contrib/website I just submitted a PR to fix a few minor issues. In general, the grammar issues here are really minimal and the page seems to communicate the project and its goals very clearly without being too distracting. I didn't find any explicit typos, like misspelled words, but I didn't look that hard either, hopefully you can help out!
  - stirner 10y ago
    Really, the typo thing was not the main point of my original comment, it was just an aside. I'm sorry to anyone I have offended. I mainly take issue with the proliferation of Go frameworks, especially HTTP frameworks. Frameworks are an antipattern and there are already a huge number of HTTP frameworks that are all incompatible and reimplement the same functionality. I don't think this is useful for the language and in fact think it hurts it.