News for hackers. Stuff that matters.
Re:Ask HN: What is the current state of web frameworks in Go... by anaganisk on Saturday July 14, 2018 @12:02AM (#17528749)
What about iris? All i see I propoganda in its docs. Is it what it actually claims?
Re:Ask HN: What is the current state of web frameworks in Go... by guessmyname on Saturday July 14, 2018 @12:16AM (#17528793)
DO NOT USE IRIS [1][2][3][4]

The author of this framework, who calls himself Kataras, is very unethical.

He fell into a big controversy with the management of his repositories, stealing several chunks of code from other popular projects without giving credits to their respective authors, and then using them to write benchmarks to make his own project look better than it is. He also spent several months creating bots to upvote his articles on different news aggregators and star his repositories to increase visibility in the GitHub Trending page. He also created several accounts in different websites (mostly Reddit) to act as a supporter of himself. The last time I heard about him, he had forked his own repositories multiple times to re-brand Iris with other names, hoping that people wouldn't notice, specially people who are just starting using Go.

[1] https://www.reddit.com/r/golang/comments/57tmp1/why_you_shou...

[2] http://www.florinpatan.ro/2016/10/why-you-should-not-use-iri...

[3] https://www.reddit.com/r/golang/comments/57w79c/why_you_real...

[4] https://github.com/avelino/awesome-go/pull/1137

Re:Ask HN: What is the current state of web frameworks in Go... by stevekemp on Saturday July 14, 2018 @12:12AM (#17528786)
Iris has been mired in drama since starting, which is good enough reason to avoid it.

One example, of many, https://github.com/avelino/awesome-go/pull/1137

Re:Ask HN: What is the current state of web frameworks in Go... by slimsag on Saturday July 14, 2018 @12:09AM (#17528773)
I've been using Go for quite a long time (since before the 1.0 release); I've never heard of Iris before.

It looks interesting, but appears to be an "all in" approach. I gather that folks who like Django may like this a lot, but for me personally it rubs me the wrong way.

This may be due to my "anti-framework" mindset, but in my experience a lot of other Go developers have this same mindset. YMMV