zlacker

[parent] [thread] 6 comments
1. mikepu+(OP)[view] [source] 2025-12-04 15:04:35
Is groovy actually really "adopted" much of anywhere? I feel like for 99% of normal people, their only real exposure to it is as the DSL of gradle and jenkins.

I can't imagine writing anything of substance primarily in groovy.

replies(3): >>xxs+q3 >>dizhn+jc >>roeger+gL1
2. xxs+q3[view] [source] 2025-12-04 15:23:34
>>mikepu+(OP)
>I can't imagine writing anything of substance primarily in groovy.

That's solely based on a poor imagination, not trying...

replies(1): >>nunobr+R7
◧◩
3. nunobr+R7[view] [source] [discussion] 2025-12-04 15:49:57
>>xxs+q3
Have to agree with the previous person. Never saw a relevant project made from Groovy. Even with Beanshell I've included it a few times in other projects for basic scripting/customization within the app but groovy? Never in 15 years to now.
replies(2): >>mikepu+Jh >>brabel+WW4
4. dizhn+jc[view] [source] 2025-12-04 16:12:59
>>mikepu+(OP)
Rundeck uses it for its plugins. It might be like how people use lua for their main program's dynamic scripting except they know Java so they use groovy.
◧◩◪
5. mikepu+Jh[view] [source] [discussion] 2025-12-04 16:36:35
>>nunobr+R7
I think embedding and testing/plugins/DSLs really is the main use-case. It's a terrible fit for a CLI tool if you've got to wait for a JVM to boot up, especially in a world where people are now used to those kinds of things being instantaneous rust or go binaries.
6. roeger+gL1[view] [source] 2025-12-05 00:18:37
>>mikepu+(OP)
Rackspace used (uses?) it.
◧◩◪
7. brabel+WW4[view] [source] [discussion] 2025-12-05 21:20:08
>>nunobr+R7
We use the Spock Framework for testing. It's the best testing framework in the JVM, no joke.
[go to top]