blackdrag

5 ms·

1.
by blackdrag 11y ago
We have not been looking for a new governance structure, that's right. That comes in the package with moving to Apache.. as would have been if we had moved to Eclipse. Moving off Codehaus had happened at that point already in several a
2.
by blackdrag 11y ago
Groovy moved from Codehaus to Apache because Codehaus was shut down. This has nothing to do with Pivotal at all. And maybe I get the word retrenched wrong, but it was not a simple reduction of people working at Groovy, it was a full layoff,
3.
by blackdrag 11y ago
vorg, some corrections for you. Only 2 of 6 did go to OCI. Another 2 did go to Gradle. And then about Alex Groovy++. At least you are not spreading the false rumors anymore that the codebase was copied. I have not seen any original ideas in
4.
by blackdrag 12y ago
there is one thing you can be very happy about... there is no Project Lead in Apache Projects, right?
5.
by blackdrag 12y ago
vorg (aka Gavin), can you proof your 2011 statement about the duplication? Neither was there a copy&paste, nor is there a big overlap in concepts that goes beyond what these would have in common with javac for example. And another thing
6.
by blackdrag 12y ago
I agree that the mailing list should have been used the same day, but are you seriously unhappy that something is announced on the mailing list with a delay of 4 days, where all of these days had been travel, conference or holiday for any
7.
by blackdrag 12y ago
Guess I am one of the ones from 2 yrs ago, even though I am not aware this has already been 2 yrs. I thought last time was already last year... well, I can be easily mistaken. But I really wonder what those Pivotal accounts are supposed to
8.
by blackdrag 12y ago
Well, I as Groovy Core don't follow hacker news normally. There are already enough channels for me to follow and the density of Groovy related themes has been quite low here. It as a thing of trying to spend the little time I have with
9.
by blackdrag 12y ago
So what's the appropriate communication way for this? I am curious to know how that should have been done
10.
by blackdrag 12y ago
Even if Groovy 3 had its first beta tomorrow, it would take several months for it to become the new 3.0. That has been the case for every Groovy version with a beta and especially for a version with so many changes as 3.0. Also the bigger t
11.
by blackdrag 14y ago
Should I have corrected your misread about the announcements? Well I would have done so if I had read it. I try to concentrate on working and what goes through the lists. I don't read blogs very often. The normal channel for me is to ask on
12.
by blackdrag 14y ago
As a main Groovy developer, the Jochen Theodorou, that was spoken of above, I think I have to correct the above quite a bit. Yes, the distribution contains 2 jars now, one for the groovy parts being precompiled with the invokedynamic port a