groovy-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Guillaume Laforge <glafo...@gmail.com>
Subject Re: About Gradle, Kotlin and Inner Fear
Date Mon, 27 Nov 2017 09:21:56 GMT
Summarizing the numbers I got with BigQuery queries for Maven vs Gradle,
and Gradle in Kotlin vs Groovy here:
http://glaforge.appspot.com/article/gradle-vs-maven-and-gradle-in-kotlin-or-groovy

Guillaume


On Mon, Nov 27, 2017 at 9:31 AM, Guillaume Laforge <glaforge@gmail.com>
wrote:

> Our of curiosity, I did a quick run through the Github dataset that is
> available through Google's BigQuery <https://bigquery.cloud.google.com>
> analytics tool.
>
> There are certainly different ways to count gradle builds, as not all are
> necessarily named build.gradle, etc, but it should give a good enough
> estimate of proportions.
> Perhaps there are better queries for double checking this. Perhaps
> developers also use a different file name than gradle.kts?
> Anyway, I ran this query to know how many build.gradle and
> build.gradle.kts build files there are on open source github repositories.
> Here's what I got.
>
> There are 414,329 build.gradle files (in Groovy).
>
>
> ​
>
> There are 207 build.gradle.kts files (in Kotlin).
>
>
>
> So that's basically one Kotlin build for 2000 Groovy builds.
>
> Guillaume
>
>
> On Mon, Nov 27, 2017 at 8:58 AM, Thibault Kruse <tibokruse@googlemail.com>
> wrote:
>
>> So, roughly 18 months later, it seems that projects are not exactly
>> flocking on hordes to kotlinscript-based gradle builds:
>> allinurl: build.gradle  -kotlin-dsl -JetBrains-kotlin site:github.com
>> 37,300
>> allinurl: build.gradle.kts -kotlin-dsl -JetBrains-kotlin site:github.com
>> 175
>>
>> And if I tried to remove all projects that are directly kotlin
>> related, that number would be even lower.
>>
>> So it seems both migrating from Groovy to Kotlin as well as starting
>> new gradle projects with kotlin instead of groovy is not very popular
>> for projects hosted on github so far, unless my google search query is
>> flawed.
>>
>> On Thu, May 26, 2016 at 2:51 AM, Suderman Keith <suderman@anc.org> wrote:
>> > I suspect a deep knowledge of the inner workings of Eclipse would be
>> > required.  You could always take a look at the code on GitHub [1] and
>> see if
>> > you can make sense of it. Although, it may not be as dead as we have
>> been
>> > led to believe (I personally use IntelliJ) as it looks like that latest
>> > SNAPSHOT was released Mar 4, 2016.
>> >
>> > Cheers,
>> > Keith
>> >
>> > REFERENCES
>> >
>> > 1. https://github.com/groovy/groovy-eclipse
>> >
>> > On May 25, 2016, at 7:22 PM, Balachandran Sivakumar <
>> benignbala@gmail.com>
>> > wrote:
>> >
>> > Hi,
>> >
>> > On Mon, May 23, 2016 at 10:02 PM, Balachandran Sivakumar
>> > <benignbala@gmail.com> wrote:
>> >>
>> >> Hi Cedric,
>> >>
>> >> On Mon, May 23, 2016 at 5:27 PM, Cédric Champeau
>> >> <cedric.champeau@gmail.com> wrote:
>> >>>>
>> >>>> there's absolutely no need for an external DSL descriptor: all the
>> >>>> constructs of the language, like extension methods or static
>> builders are
>> >>>> first class language features. The issue is, IDE support for Groovy
>> is
>> >>>> lacking (Groovy Eclipse is dead, IntelliJ needs to know specifics
of
>> static
>> >>>> Gradle/Groovy scripts, ...)
>> >>
>> >>
>> >> If we have to resurrect it, what would it take ? I mean, what skill
>> >> set/knowledge should someone have to work on it and resurrect it ?
>> Also,
>> >> can someone here help with that effort ? Thanks
>> >>
>> >
>> >     Can someone please help with this ? What would it take for someone
>> with
>> > reasonable Groovy/Java knowledge to pick up Goovy Eclipse and maintain
>> it ?
>> > Thanks
>> >
>> > --
>> > Thank you
>> > Balachandran Sivakumar
>> >
>> >
>> > ------------------------------
>> > Research Associate
>> > Department of Computer Science
>> > Vassar College
>> > Poughkeepsie, NY
>> >
>>
>
>
>
> --
> Guillaume Laforge
> Apache Groovy committer & PMC Vice-President
> Developer Advocate @ Google Cloud Platform
>
> Blog: http://glaforge.appspot.com/
> Social: @glaforge <http://twitter.com/glaforge> / Google+
> <https://plus.google.com/u/0/114130972232398734985/posts>
>



-- 
Guillaume Laforge
Apache Groovy committer & PMC Vice-President
Developer Advocate @ Google Cloud Platform

Blog: http://glaforge.appspot.com/
Social: @glaforge <http://twitter.com/glaforge> / Google+
<https://plus.google.com/u/0/114130972232398734985/posts>

Mime
View raw message