3 ms·
The company I work for has released a couple products in grails (SaaS). Ultimately, it's basically a "wrapper" around very common Java tech (like Spring WebMVC)
by rnovak 11y ago
The company I work for has released a couple products in grails (SaaS). Ultimately, it's basically a "wrapper" around very common Java tech (like Spring WebMVC). It's really nice to use to build things quickly, but when Groovy was dropped by their main sponsor (Pivotal), our company kind of lost faith in the future of the language.
- vorg 11y agoSince Grails 3.0, Grails is a wrapper around Gradle also. The Grails 1.0 backing company G2One,Inc got bought by SpringSource a year after it was formed, which was the true purpose of Grails bundling Spring, i.e. to muscle in on SpringSource's consulting business until it hurt. So I guess the true purpose of Grails 3.0 bundling Gradle is for OSI's Grails consulting arm to get bought by Gradleware to similarly protect its Gradle consulting cashflow. Earlier this year, Grails' previous backer Pivotal,Inc dropped sponsorship of Grails effective a few days before Grails 3.0 was released, which was very conveniently picked up by OSI,Inc, minus 4 mainly Groovy developers who were retrenched. It all looked like a cost cutting exercise by the Grails P.M. in disguise. The lack of scruples in the people behind Grails is reason enough to ignore it.