This is good news I think. Hopefully this gets Groovy and Grails some much needed visibility.
Graeme Rocher's Blog: Groovy and Grails join the Spring family
SpringSource Team Blog: More Weapons for the War on Complexity: SpringSource Acquires Groovy/Grails Leader
Showing posts with label Grails. Show all posts
Showing posts with label Grails. Show all posts
Tuesday, November 11, 2008
Friday, June 06, 2008
Grails 1.0.3 Released
Graeme Rocher announced the release of Grails 1.0.3 this morning. Great news, time to upgrade my apps!
Read Graeme's post
Read Graeme's post
Wednesday, April 16, 2008
Mastering Grails
Scott Davis has posted "Mastering Grails: Many-to-many relationships with a dollop of Ajax" in the Mastering Grails series. If anyone can master Grails; it would be Scott Davis. Have a look.
Tuesday, February 05, 2008
Grails 1.0 Released
Graeme Rocher, from G2One Inc., announced the release of Grails 1.0 this morning. The release notes are available from grails.org.
If you're a Java person and aren't familiar with Grails or Groovy for that matter, you should definitely check out Grails. Grails is a rapid web application development framework based on convention over configuration. It is designed MUCH like Ruby-on-Rails, but built using Groovy as a language. The main benefits of this approach is that Groovy is based on Java; which means it looks and feels like Java. This helps introduce it to a team and lower the learning curve. The other benefit is that it builds down to a WAR file that you can deploy into any old application server. No special hackery required. This is important when deploying it into a very 'enterprisey' environment.
Also, the internals of Grails and how it works are not based on it's own invented voodoo. Grails uses Spring, Hibernate, and Acegi internally. Good stuff...
If you're a Java person and aren't familiar with Grails or Groovy for that matter, you should definitely check out Grails. Grails is a rapid web application development framework based on convention over configuration. It is designed MUCH like Ruby-on-Rails, but built using Groovy as a language. The main benefits of this approach is that Groovy is based on Java; which means it looks and feels like Java. This helps introduce it to a team and lower the learning curve. The other benefit is that it builds down to a WAR file that you can deploy into any old application server. No special hackery required. This is important when deploying it into a very 'enterprisey' environment.
Also, the internals of Grails and how it works are not based on it's own invented voodoo. Grails uses Spring, Hibernate, and Acegi internally. Good stuff...
Subscribe to:
Posts (Atom)