Is it time for D 3.0?

[Paulo Pinto]

On Sunday, 29 March 2020 at 23:27:06 UTC, Meta wrote:
> On Sunday, 29 March 2020 at 12:00:20 UTC, Paulo Pinto wrote:
>> On Sunday, 29 March 2020 at 09:47:15 UTC, Russel Winder wrote:
>>> On Sat, 2020-03-28 at 11:01 +0000, Paulo Pinto via 
>>> Digitalmars-d wrote:
>>>> […]
>>>> 
>>>> Groovy isn't properly a good exemple.
>>>
>>> I see no reason why it isn't, it is an evolving language 
>>> following the semantc versioning model.
>>>
>>>> If it wasn't for Gradle and its use in Android, it would be 
>>>> long gone and forgotten.
>>>
>>> In you opinion. The evidence I see is that Groovy has more 
>>> traction in Java sites than is immediately apparent. Clearly 
>>> Kotlin is challenging the role of Groovy in many respects, 
>>> but Groovy is still used by many orgsanisation fro dynamic 
>>> programing. The analogy is where C++ codebases use Python or 
>>> Lua.
>>>
>>>> And even there, there is a big pressure to replace it with 
>>>> Kotlin, in what regards Android build infrastructure.
>>>
>>> Kotlin rather than Groovy is the language of choice on the 
>>> Android platform these days certainly, but there are a lot of 
>>> JVM installation out there using Java, Kotlin, and Groovy – 
>>> not to mention Scala, Clojure, etc. – all going along 
>>> happily. Yes there are a lot of those installations that will 
>>> only use Java.
>>>
>>>> So is the fate of any guest language until the main platform 
>>>> language catches up.
>>>
>>> Java can never catch up with Groovy, whereas is can catch up 
>>> with Kotlin. Kotlin is the guest language you are talking of 
>>> for most Java installation, not Groovy. Statis Groovy may be 
>>> a dead thing, but Dynamic Groovy is far from dead.
>>
>> The times that Groovy made any headlines in German Java 
>> conferences or local JUGs are long gone, I wonder where Groovy 
>> is being used above a single digit usage market share on the 
>> Java platform.
>
> IBM Security, one of the largest cybersecurity companies in the 
> world. The most widely used enterprise-level SIEM (by quite a 
> wide margin) uses Groovy extensively for its testing framework.

The same IBM that introduced Beanshell for scripting Java beans, 
once upon time used JTcl for Websphere scripting until version 6, 
replaced it with jython on Websphere 6 and now just offers JMX 
MBeans on Liberty?

Yep, definitely a guarantee of longevity regarding IBM's usage of 
JVM guest languages.