<p>Couldn't found a suitable chatting app backend so i decide build myself. Its still early stage but hope can get more dev power.</p>
<p><a href="https://github.com/cmingxu/chat-example" rel="nofollow">https://github.com/cmingxu/chat-example</a></p>
<hr/>**评论：**<br/><br/>vishnuv: <pre><p><a href="http://www.mattermost.org/" rel="nofollow">http://www.mattermost.org/</a> . <a href="https://github.com/mattermost" rel="nofollow">https://github.com/mattermost</a> . This is the most successful open source slack alternative in golang.</p></pre>anonxgh: <pre><p>By successful you mean what? Funded by VC?</p>
<p>I don't want to hurt anyone's feelings, but my humble opinion is their architecture (or rather lack of it) is a disaster. E.g. look at <a href="https://github.com/mattermost/platform/blob/master/web/web.go" rel="nofollow">this</a> <strong>1174 lines</strong> or <a href="https://github.com/mattermost/platform/blob/master/api/user.go" rel="nofollow">this</a> <strong>1782 lines</strong> of masterpiece in a single file. Can it be simplified and/or split into multiple files?</p>
<p>I don't like haters and don't want to become one. BUT, I'm dead sure at the end we'll see one more article on "how bad monolith is", "microservices rock", "go is so special it doesn't need web-frameworks". Of course, they we'll compare a crappily implemented monolith to less crappy microservices and make big conclusions out of it.</p></pre>icholy: <pre><p>Wut?</p></pre>shazow: <pre><p>Some suggestions: A readme, maybe some screenshots. What are your goals?</p>
<p>Not sure what you mean by chatting app "backend", but you might like my ssh-chat project: <a href="https://github.com/shazow/ssh-chat" rel="nofollow">https://github.com/shazow/ssh-chat</a></p>
<p>I'm also building an IRC server toolkit in Go: <a href="https://github.com/shazow/go-irckit" rel="nofollow">https://github.com/shazow/go-irckit</a></p></pre>
