Okay folks, it's time for THE question. @Groovy Duke I'm tagging you since it looks like you are "the one who knows". When are we going to have a Grails version with just a Micronaut dependency?

No time soon. Last I talked to the Grails team they were working hard on Grails 7, which would include Groovy 4, Spring Boot 3.x, which comes with supporting new java versions, also figuring bout what to do with GORM and Hibernate deprecating Criteria. I'm not sure what else of hand. I know a while ago I head someone say that Grails would always be based on spring boot. I think that was premature as Grails now uses Micronaut for the default context, and has various integrations. I think the future underlying of Grails is Micronaut. There is one person who disagrees and created a fork of Grails that turns back time to when it was purely Spring Boot. I don't think the fork has much of a chance beyond being a personal project. More recently(start of this year)I stopped going to the Grails meetings as I just started a new job at a startup, where I'm using Micronaut instead of Grails. I do miss the convention over configuration, however that does give me more incentive to resurrect my side project of bringing conventional over configuration to Micronaut, but I have to find time to do that project. Now it's also worth noting that the Grails team has expanded from just Puneet, and help when he needed it, to having several more dedicated members and another active community members.

Yep, the JPA API is a problem I hope someone with time and money can build an API on top of it, cause at the moment I can only see it as a step-back, no matter how faster it is.

yeah, I am the person who created a fork of Grails, it’s Grace now available on SDKMan, you can give it a try.

Well it's good to have options, just in case. Grails has a development experience that is too good to be left behind

I know you created the fork I just didn't feel the need to advertise it, because unless you have financial backing and a team working on it, I don't see it being anything more than a personal pet project. Grails and by extension your fork, is too big of an ecosystem for one person to manage it on their own for very long. Agree to disagree about the future of Grails. How does Spring Boot have better support for Groovy? I would have to see some specific cited examples to really believe that. So far working with Micronaut on a daily basis with Groovy, and the support seems fine to me. I don't put much stock in what is popular, in polls for surveys. Just because something is popular doesn't make it good or the right tool for the job. Also the JetBrains survey is inherently biased. giangio I agree the Grails developer experience is really good as I worked using it for the past 12 years through 5 different jobs and 7 different companies. To stay relevant and maintain their niche Grails will have to continue to do what they have done over the years, evolve.

Spring Boot CLI provides a feature that let users to run Groovy scripts without much boilerplate code, so we can use to quickly prototype with Spring. This shows us the power of Groovy as a dynamic language, but Grails doesn’t provide that. There are some really great designs in there that are worth learning from. https://docs.spring.io/spring-boot/docs/2.7.18/reference/htmlsingle/#getting-started.installing.cli.quick-start Grails is very difficult to do this, and I’ve rewritten almost all of the low-level code in Grails for Groovy Transformation, Grails Artefact, and Trait. I knew that Graeme Rocher was also trying to implement this feature called

web-micro

, but gave up. You can see the final result in my Twitter post. https://twitter.com/rainboyan/status/1675398578154659840