<p>Or would this totally go against Golang's philosophy? I'm still working on groking Go and some articles I've read have been adamant about the fact that Go's methodology is anti-"magic".</p>
<hr/>**评论:**<br/><br/>_medved_: <pre><p>There's already revel. Very similar to rails.</p>
<p><a href="https://github.com/revel/revel" rel="nofollow">https://github.com/revel/revel</a></p></pre>RIC_FLAIR-WOOO: <pre><p>Beego works very well, though I skipped the ORM for using sqlx. You probably aren't ever going to get something like ActiveRecord in Go.</p></pre>Bromlife: <pre><p>Stuff like that exists already. There's gorm, for example.</p>
<p>But I don't think they'll get a lot of traction in the long run. For the magic you gain you lose the inherent speed that Go provides. You may as well stick with a dynamic language in that case.</p></pre>thoughtquery: <pre><p>How bad is the performance loss?</p></pre>Bromlife: <pre><p>Don't know. I investigated them when I first started coding in Go. The community turned me off the idea and now I'm happy with Sqlx.</p></pre>Streamweaver66: <pre><p>Depending on what you mean by like rails, we may or may not even need it. That said BeeGo and Revel are go to MVC(ish) frameworks. Revel is billed as a "roll your own ORM" and you have to write your own transnational handling. I don't feel like we have a good option in Go right now in general. </p></pre>emadera52: <pre><p>Another satisfied Beego user. It doesn't do <em>everything</em> Rails does, but it does most of what you need. The big difference is the learning curve. Compared Beego, the Rails learning curve is a mountain. To be fair I only made it about 2/3 of the way up before saying "Screw it, this can't be the best way to do build a web site."</p>
<p>Compared to Beego, Revel tends to rely on magic a lot more. Once you have a good grasp of Go, you're well on your way to understanding and effectively using Beego. You'll need to take more on faith when using Revel.</p></pre>Raiyni: <pre><p>Beego is basically RoR but is slow as hell. </p></pre>Bromlife: <pre><p>My simple rule is if it uses reflection, it's probably not the best solution. </p></pre>tieubao: <pre><p>Our team use beego for some long run projects. Why do you say that?</p></pre>Raiyni: <pre><p>Because it is. <a href="https://github.com/julienschmidt/go-http-routing-benchmark" rel="nofollow">https://github.com/julienschmidt/go-http-routing-benchmark</a></p></pre>
这是一个分享于 的资源,其中的信息可能已经有所发展或是发生改变。
入群交流(和以上内容无关):加入Go大咖交流群,或添加微信:liuxiaoyan-s 备注:入群;或加QQ群:692541889
- 请尽量让自己的回复能够对别人有帮助
- 支持 Markdown 格式, **粗体**、~~删除线~~、
`单行代码`
- 支持 @ 本站用户;支持表情(输入 : 提示),见 Emoji cheat sheet
- 图片支持拖拽、截图粘贴等方式上传