Return-Path: X-Original-To: apmail-groovy-users-archive@minotaur.apache.org Delivered-To: apmail-groovy-users-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id CCF6F17305 for ; Tue, 28 Apr 2015 03:06:45 +0000 (UTC) Received: (qmail 69833 invoked by uid 500); 28 Apr 2015 03:06:45 -0000 Delivered-To: apmail-groovy-users-archive@groovy.apache.org Received: (qmail 69790 invoked by uid 500); 28 Apr 2015 03:06:45 -0000 Mailing-List: contact users-help@groovy.incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@groovy.incubator.apache.org Delivered-To: mailing list users@groovy.incubator.apache.org Received: (qmail 69779 invoked by uid 99); 28 Apr 2015 03:06:45 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 28 Apr 2015 03:06:45 +0000 X-ASF-Spam-Status: No, hits=3.2 required=5.0 tests=HTML_IMAGE_ONLY_32,HTML_MESSAGE,SPF_SOFTFAIL X-Spam-Check-By: apache.org Received-SPF: softfail (nike.apache.org: transitioning domain of emacadie@gmail.com does not designate 54.76.25.247 as permitted sender) Received: from [54.76.25.247] (HELO mx1-eu-west.apache.org) (54.76.25.247) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 28 Apr 2015 03:06:20 +0000 Received: from mail-lb0-f176.google.com (mail-lb0-f176.google.com [209.85.217.176]) by mx1-eu-west.apache.org (ASF Mail Server at mx1-eu-west.apache.org) with ESMTPS id A4E8A2156D for ; Tue, 28 Apr 2015 03:06:18 +0000 (UTC) Received: by lbcga7 with SMTP id ga7so97032721lbc.1 for ; Mon, 27 Apr 2015 20:06:18 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=aSzIyIEOQHoQ2GBIjt/s8k7Eo/EkAi2THjMoLQGBXaE=; b=RGjRSJPLh0AMlqO9/JYpYircc0Yc/uPgNFsjjzaVt3hh72GRU6MyIc4z9KqDjps2Kr iGahiAMrfdXn0lifdT5Hj/peWHFHHdSBfKD7n7XAwfB6MTHsjeZh1FvA7A5fAepId7Ig H7LK/Ox7Pm7L9ycef3lLnLLfbFncYdKTiHOONESnpnfcy4Qpifuyjjl+tFY+hwnhaH4t UKEprQ3VGZmqCJSSA5gPsYIaQ4EcIQ5ucm/HHCAKf3vK5p86Iav292kEPpjUEB9xZ1uq iGUM5JUn8fYysals5S5T3ksm+loajyGo1OIv+il4ffBxQUhIE4opfargJv+MMomW4fRa 1bCw== MIME-Version: 1.0 X-Received: by 10.152.115.173 with SMTP id jp13mr12462155lab.119.1430190378201; Mon, 27 Apr 2015 20:06:18 -0700 (PDT) Received: by 10.112.37.138 with HTTP; Mon, 27 Apr 2015 20:06:18 -0700 (PDT) Date: Mon, 27 Apr 2015 22:06:18 -0500 Message-ID: Subject: Why aren't more people looking at Groovy? From: Eric MacAdie To: users@groovy.incubator.apache.org Content-Type: multipart/alternative; boundary=001a11c235dc7438d10514c02565 X-Virus-Checked: Checked by ClamAV on apache.org --001a11c235dc7438d10514c02565 Content-Type: text/plain; charset=UTF-8 I started this discussion on the old list, and someone said it should be brought here. Here is my original post: *In addition to Groovy, I am also interested in Clojure. I found an interesting article on the Clojure reddit: "Our curvy road to Clojure" at http://inside.unbounce.com/product-dev/our-curvy-road-to-clojure/ * *The basic gist of the article is that they were a Java and Ruby shop, and they realized that combination was not working as well as they hoped, so they started looking for alternatives. They tried JRuby and Scala, before settling on Clojure.* *What I find odd is he never mentions looking at Groovy. I hear and read a lot about shops that start out using Java and pick up Ruby, and some of them eventually realize that the chocolate and the peanut butter do not mix as well as they had hoped. So they look for something else. Yet I never hear about any of them looking at Groovy. It seems like if you are using Java for heavy lifting and Ruby for more dynamic/agile work that Groovy would be a great fit.* *Has anyone else noticed this? Any thoughts?* I left a comment on the Unbounce blog asking if they looked at Groovy, and here is the response: *In their pre-Unbounce lives, several of us have had experience with Groovy, from short embedded scripts to full blown Grails apps ; thus we have a good grasp of the language.* *There's no doubt that Groovy has some very strong points, including closures, progressive typing, null-safe property navigation and tons of smart extensions to the JDK. But the fact the language is mutable by default and supports meta-programming (expando meta-class), has the capacity to complicate things. If you've worked on a non-trivial Grails application, I'm sure sure you know what I mean.* *Moreover, from a pure perception standpoint, despite 12 years of existence, Groovy seems to have stayed a niche language. Its tumultuous past and uncertain future, doesn't help deciding to bet the house on it. The addition of closures and streaming API to Java, the rise of Rx, makes a massive shift towards Groovy less likely in the future.* *Considering all of these, Clojure seemed a safer choice. There's a strong language theory behind it. Its community is vibrant, opinionated and pragmatic, a rare combination in our industry.* *We'll see in the future if our bet was right or not. In the meantime, what a great ride :)* = Eric MacAdie --001a11c235dc7438d10514c02565 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
I started this discussion on the old list, and someone sai= d it should be brought here.

Here is my original post:
=

In addition to Groovy, I am also interested in Clojure. I found an interesting article on the Clojure reddit: "Our curvy road t= o=20 Clojure" at http://inside.unbounce.com/product-de= v/our-curvy-road-to-clojure/

The basic gist of the article is that they were a Java and Ruby shop, and=20 they realized that combination was not working as well as they hoped, so they started looking for alternatives. They tried JRuby and Scala,=20 before settling on Clojure.

What I find odd is he never= mentions looking at Groovy.

I hear and read a lot about shops that start out using Java and pick up=20 Ruby, and some of them eventually realize that the chocolate and the=20 peanut butter do not mix as well as they had hoped. So they look for=20 something else. Yet I never hear about any of them looking at Groovy. It seems like if you are using Java for heavy lifting and Ruby for more=20 dynamic/agile work that Groovy would be a great fit.

Ha= s anyone else noticed this? Any thoughts?
I left a comment on the Unbounce blog asking if they looked at Groovy, a= nd here is the response:

In their pre-Unbounce lives, several of us have had experience with= =20 Groovy, from short embedded scripts to full blown Grails apps ; thus we=20 have a good grasp of the language.

There's no doubt that G= roovy=20 has some very strong points, including closures, progressive typing,=20 null-safe property navigation and tons of smart extensions to the JDK.=20 But the fact the language is mutable by default and supports=20 meta-programming (expando meta-class), has the capacity to complicate=20 things. If you've worked on a non-trivial Grails application, I'm s= ure=20 sure you know what I mean.

Moreover, from a pure perception=20 standpoint, despite 12 years of existence, Groovy seems to have stayed a niche language. Its tumultuous past and uncertain future, doesn't help= =20 deciding to bet the house on it. The addition of closures and streaming=20 API to Java, the rise of Rx, makes a massive shift towards Groovy less=20 likely in the future.

Considering all of these, Clojure seemed= a=20 safer choice. There's a strong language theory behind it. Its community= =20 is vibrant, opinionated and pragmatic, a rare combination in our=20 industry.

We'll see in the future if our bet was right or = not. In the meantime, what a great ride :)


=3D Eric Ma= cAdie

--001a11c235dc7438d10514c02565--