Err... my bad, just to make it clear, I was not part of the decision, I am just a Grails user at the moment. But I did not understand the rationale behind that decision, I think there must be good reasons to add any dependency, especially when they add 100Mb to the final jar and increase the costs of maintaining the whole project.
A part of me is still fighting to not complain more than I am already doing :) Gianluca Sartori -- https://dueuno.com On Wed, 17 Jun 2026 at 12:38, Jochen Theodorou <[email protected]> wrote: > > > On 6/17/26 10:22, Gianluca Sartori wrote: > >> > >> Furthermore... what is the actual story for the user for having Grails > >> on top of Micronaut in the first place if Grails does not plan to go > >> away from Spring to Micronaut? > >> > > > > That was my question at the beginning of the new Grails community driven > > process, the reason was mostly due to the better HttpClient that > Micronaur > > had at the time. > > I did read the 2024 voting on github yesterday. The declarative client? > Wasn't that already done with in Grails 7? > > > Now we (finally) have a ton of them in Spring and Apache for any level of > > abstraction you need/prefer to make a service call. > > > > And BTW, my work has been very much inspired by the Grails & Micronaut > > developers and I am a fan of the people who brought Groovy & Grails to > the > > universe. > > But the architect in me is kicking my balls every time he can for the > > decision of including Micronaut (which I love and appreciate) in Grails. > > Being a software architect also means to review decisions and correct > them. So do not kick too hard. Believe me, I did some things in Groovy I > am not happy with today and try to fix them in the long term. > > But what I get is: there is no real justification left for having > Micronaut in Grails from a technical perspective. > > bye Jochen >
