Django -vs- Grails -vs-？ [英] Django -vs- Grails -vs-?
问题描述
Django是一个非常有效的框架，用于构建内容繁重的网站;与之前的一些Java怪物相比，我尝试过的最好和新鲜空气的呼吸。然而，它是用Python编写的，这意味着部署/打包，调试，分析器和其他工具的方式几乎没有真正的支持，使构建和维护应用程序变得更加容易。
Ruby具有类似的问题，尽管我比Ruby更好地支持Ruby ，但我的印象是Rails大致相同在Django的船只管理/支持应用程序。
有没有人在这里尝试过用于非平凡项目的Django和Grails（或其他Web框架）？他们是如何比较的？
你问过使用Grails和Django的人。我已经为大项目做了两件事。这是我的想法：
IDE的：
Django在Eclipse中工作得很好，Grails在IntelliJ Idea中工作得很好。 >
调试：
实际上相同（假设您使用IntelliJ for Grails，Eclipse for Python）。步骤调试，检查变量等，不需要打印语句。有时候，django错误消息可能是无用的，但Grails错误消息通常很漫长而难以解析。
运行单元测试的时间
django：2秒。
Grails：20秒（测试本身都运行在几分之一秒钟内，它是关于加载框架来运行它们的部分，它们将占用其余部分，如您所见，Grails的加载速度很慢） 。
部署：
Django：copy&将一个文件粘贴到apache配置中，并重新部署，只需更改代码并重新加载apache即可。
Grails：创建一个.war文件，将其部署在tomcat上，冲洗并重复重新部署。
编程语言
Groovy真的太棒了我喜欢它，比Python更好。但我肯定没有投诉。
插件：
Grails：大量破坏的插件（并且可以使用每个java lib）。
Django：几个稳定的插件，但足以做大部分你需要的。
数据库：
Django ：使用南方的模式迁移，以及一般直观的关系。
Grails：没有模式迁移，默认情况下它会在启动时删除数据库... WTF
用法：
Django：创业公司（特别是在Gov 2.0的空间），独立的web开发商店。
Grails：企业
希望有帮助！
I'm wondering if there's such a thing as Django-like ease of web app development combined with good deployment, debugging and other tools?
Django is a very productive framework for building content-heavy sites; the best I've tried and a breath of fresh air compared to some of the Java monstrosities out there. However it's written in Python which means there's little real support in the way of deployment/packaging, debugging, profilers and other tools that make building and maintaining applications much easier.
Ruby has similar issues and although I do like Ruby much better than I like Python, I get the impression that Rails is roughly in the same boat at Django when it comes to managing/supporting the app.
Has anyone here tried both Django and Grails (or other web frameworks) for non-trivial projects? How did they compare?
You asked for someone who used both Grails and Django. I've done work on both for big projects. Here's my Thoughts:
IDE's: Django works really well in Eclipse, Grails works really well in IntelliJ Idea.
Debugging: Practically the same (assuming you use IntelliJ for Grails, and Eclipse for Python). Step debugging, inspecting variables, etc... never need a print statement for either. Sometimes django error messages can be useless but Grails error messages are usually pretty lengthy and hard to parse through.
Time to run a unit test: django: 2 seconds. Grails: 20 seconds (the tests themselves both run in a fraction of a second, it's the part about loading the framework to run them that takes the rest... as you can see, Grails is frustratingly slow to load).
Deployment: Django: copy & paste one file into an apache config, and to redeploy, just change the code and reload apache. Grails: create a .war file, deploy it on tomcat, rinse and repeat to redeploy.
Programming languages: Groovy is TOTALLY awesome. I love it, more so than Python. But I certainly have no complaints.
Plugins: Grails: lots of broken plugins (and can use every java lib ever). Django: a few stable plugins, but enough to do most of what you need.
Database: Django: schema migrations using South, and generally intuitive relations. Grails: no schema migrations, and by default it deletes the database on startup... WTF
Usage: Django: startups (especially in the Gov 2.0 space), independent web dev shops. Grails: enterprise
Hope that helps!
这篇关于Django -vs- Grails -vs-？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
