someone invents a new language or approach and everyone flocks to it because it is simple and they can understand it and start assembling complexity on top of that ... (Gradle, which Tim refers to, btw, is a perfect example of that ...)
Unfortunately, Gradle chose Groovy for its programming interface, and Groovy was designed to be complex so its backers could sell conferences, courses, and consultants. Thankfully, it looks like Gradle's going polyglot soon, their Gradle 2 roadmap [1] talks about a configuration-on-demand build model which could expose an API usable by any scripting language, like with vertX.
I've noticed you relentlessly and persistently post comments that are deeply critical of Groovy. To put it bluntly, I pretty much ignore everything you say on this topic because I have surmised that you have some deep issue or axe to grind that is beneath it all. I am curious however what that deeper issue is. Clearly from your depth of knowledge you had a heavy involvement at some point, but at some point something deeply alienated you. I am not casting a judgement here about whether you're justified in that, but I like to keep an open mind. If you are willing to tell me (privately if necessary) I am interested to know what your side of the story actually is.
I don't note which username I'm replying to when I post a comment because it seems many HN commenters use many different usernames, but I can avoid replying to yours if you like. As for my deep issue or axe to grind, nowadays I try to avoid talking about my personal motives because in the past people have used that to deflect attention away from tech issues and timelines and use cases and the stuff that matters, so I'll decline your invitation.
I post comments about and replies to stuff that interests me such as Groovy, including the org.codehaus.groovy implementation. You mentioned your take on Gradle and the simplicity/complexity cycle, and I was giving my opinion on it.
Comments
Unfortunately, Gradle chose Groovy for its programming interface, and Groovy was designed to be complex so its backers could sell conferences, courses, and consultants. Thankfully, it looks like Gradle's going polyglot soon, their Gradle 2 roadmap [1] talks about a configuration-on-demand build model which could expose an API usable by any scripting language, like with vertX.
[1] http://forums.gradle.org/gradle/topics/revolutionary_new_gra...
I've noticed you relentlessly and persistently post comments that are deeply critical of Groovy. To put it bluntly, I pretty much ignore everything you say on this topic because I have surmised that you have some deep issue or axe to grind that is beneath it all. I am curious however what that deeper issue is. Clearly from your depth of knowledge you had a heavy involvement at some point, but at some point something deeply alienated you. I am not casting a judgement here about whether you're justified in that, but I like to keep an open mind. If you are willing to tell me (privately if necessary) I am interested to know what your side of the story actually is.
I don't note which username I'm replying to when I post a comment because it seems many HN commenters use many different usernames, but I can avoid replying to yours if you like. As for my deep issue or axe to grind, nowadays I try to avoid talking about my personal motives because in the past people have used that to deflect attention away from tech issues and timelines and use cases and the stuff that matters, so I'll decline your invitation.
I post comments about and replies to stuff that interests me such as Groovy, including the org.codehaus.groovy implementation. You mentioned your take on Gradle and the simplicity/complexity cycle, and I was giving my opinion on it.