3 ms·
> My current direction, which I was all set to get serious with today, was to use Groovy on Grails Is that version 2 or 3 of Grails? Virtually no-one has updat
by vorg 9y ago
> My current direction, which I was all set to get serious with today, was to use Groovy on Grails
Is that version 2 or 3 of Grails? Virtually no-one has updated their Grails 2 websites to version 3, or is starting new projects in Grails 3. Choosing version 3 means first adopter risk.
- TheRealDunkirk 9y agoSo I'm quickly discovering. The problem is that I know the kinds of changes Rails introduces from one major revision to the next. If Grails follows that pattern, I don't really want to get started with 2.x, knowing that I'll have to relearn a lot of things on 3.x. It's a bit of a chicken-and-egg problem.
- mgkimsal 9y ago> Choosing version 3 means first adopter risk. I upgraded a couple v2 to v3, mostly because of concern about security (moderately sensitive data, most of the 2-era plugins aren't updated, etc). The allure of v3 was supposed to be "it's all spring boot!" but... I'm not capable enough of just installing random spring stuff and configuring it for boot - there's still 'stuff' grails does its own way (or... it's just my competency level?) But if I need to become much more proficient in spring boot to get benefit from grails 3... i'll just move to spring boot in the long haul. This seemed an inevitable move for grails, but not one I was excited about.