Grails vs Kohana: What are the differences?
What is Grails? An Open Source, full stack, web application framework for the JVM. Grails is a framework used to build web applications with the Groovy programming language. The core framework is very extensible and there are numerous plugins available that provide easy integration of add-on features.
What is Kohana? An elegant HMVC PHP5 framework. Kohana is an elegant, open source, and object oriented HMVC framework built using PHP5, by a team of volunteers. It aims to be swift, secure, and small.
Grails and Kohana belong to "Frameworks (Full Stack)" category of the tech stack.
"Groovy" is the primary reason why developers consider Grails over the competitors, whereas "Open source" was stated as the key factor in picking Kohana.
Grails and Kohana are both open source tools. It seems that Grails with 2.48K GitHub stars and 945 forks on GitHub has more adoption than Kohana with 1.61K GitHub stars and 464 GitHub forks.
According to the StackShare community, Grails has a broader approval, being mentioned in 47 company stacks & 22 developers stacks; compared to Kohana, which is listed in 3 company stacks and 3 developer stacks.
What is Grails?
What is Kohana?
Need advice about which tool to choose?Ask the StackShare community!
Sign up to add, upvote and see more prosMake informed product decisions
What are the cons of using Grails?
What are the cons of using Kohana?
Sign up to get full access to all the companiesMake informed product decisions
Sign up to get full access to all the tool integrationsMake informed product decisions
Some may wonder why did we choose Grails ? Really good question :) We spent quite some time to evaluate what framework to go with and the battle was between Play Scala and Grails ( Groovy ). We have enough experience with both and, to be honest, I absolutely in love with Scala; however, the tipping point for us was the potential speed of development. Grails allows much faster development pace than Play , and as of right now this is the most important parameter. We might convert later though. Also, worth mentioning, by default Grails comes with Gradle as a build tool, so why change?