"It’s gonna work good on all devices." Don't they mean work well?
The project creator is not a native English speaker. Let it go.
Iris: Fast back-end web framework for Go
11–20 of 125 posts
Re: Iris: Fast back-end web framework for Go
#12Not 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.
Because being a native english speaker has a lot to do with the quality of code, how rude..
Re: Iris: Fast back-end web framework for Go
#13Features: https://kataras.gitbooks.io/iris/content/features.html (seems to be missing a data/SQL/ORM layer) Usage docs for rest api: https://kataras.gitbooks.io/iris/content/render_rest.html#us...
Not including an ORM layer does not decrease "value" of this framework, because you can attach such lib on your own. In Go the you are very flexible to set up a "a place where data will be stored/queried" - there is fabulous database/sql (or additional layers like lib/pq [1]) which is great for many use cases; also orm-like solutions like gocraft/dbr [2]; oh, I also should mention Gorm [3] or Bolt [4]. Setting them up is really easy in any Go web frameworks because (almost) all database modules rely on abstraction from stdlib.
[2] https://github.com/gocraft/dbr
Re: Iris: Fast back-end web framework for Go
#14Not 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.
Because being a native english speaker has a lot to do with the quality of code, how rude..
Typos are easily checked by dictionary - no need to be native speaker for that :)
Re: Iris: Fast back-end web framework for Go
#15Any time I see a chart about web server performance without displaying the corresponding error rate and latency numbers I start to think that the author does not understand the performance aspect of HTTP services entirely.
Re: Iris: Fast back-end web framework for Go
#16Not 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.
Because being a native english speaker has a lot to do with the quality of code, how rude..
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.
Re: Iris: Fast back-end web framework for Go
#17Earlier quoted context omitted.
Because being a native english speaker has a lot to do with the quality of code, how rude..
Typos are easily checked by dictionary - no need to be native speaker for that :)
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.
Re: Iris: Fast back-end web framework for Go
#18The performance comes from using https://github.com/valyala/fasthttp instead of the stdlib net/http. From this project's FAQ: >Why creating yet another http package instead of optimizing net/http? Because net/http API limits many optimization opportunities.
And then you got your database and you speed is comparable to the rest of the world :)
What I think could work is a pure in memory database with server combination. Something like redis for websites.
Re: Iris: Fast back-end web framework for Go
#19Features: https://kataras.gitbooks.io/iris/content/features.html (seems to be missing a data/SQL/ORM layer) Usage docs for rest api: https://kataras.gitbooks.io/iris/content/render_rest.html#us...
Not including an ORM layer does not decrease "value" of this framework, because you can attach such lib on your own. In Go the you are very flexible to set up a "a place where data will be stored/queried" - there is fabulous database/sql (or additional layers like lib/pq [1]) which is great for many use cases; also orm-like solutions like gocraft/dbr [2]; oh, I also should mention Gorm [3] or Bolt [4]. Setting them u…
That's true; the same could be said for many other parts of the stack, including several features that were included, like TypeScript compilation.
Given that interacting with a database is at least as common a webdev task as, say, i18n, I thought it was worth noting that this framework does not have a db solution of choice.
Re: Iris: Fast back-end web framework for Go
#20Earlier quoted context omitted.
Because being a native english speaker has a lot to do with the quality of code, how rude..
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.
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.