Gavin Grover's GROOVY Wikiblog

See later entries

11 January 2013

Groovy's thug steals another project

In a Grales mailing list reply, Graeme Rocher on 13 Dec 2012 said "Grails, Gradle (and now Vert.x) are however significant vectors for Groovy adoption" (beginning of paragraph 2, just before he uses the word "FUD" twice to dismiss the opinions of two different people without giving any evidence of either). His reference to vert.x seemed weird, being out of context to anything being discussed.

But Rocher's sociopathic scheming hand came to light 3 weeks later, when the vert.x creator Tim Fox wrote about how VMWare bullied him into handing over ownership of the vert.x project, a move widely condemned by many in the open source programming community. Rocher's earlier reference to Vert.x was a claim of ownership by one of VMWare's thugs of his intention to steal that Apache-licensed project, just like he stole the Groovy Language (also Apache-licensed) to use in Grales. Rocher already knew then that "VMware's lawyers would turn up on Fox's door in person with a letter demanding he give up all administrative rights of the Vert.x GitHub project, Google group, vertx.io domain and Vert.x blog". Rocher was probably the corporate hitman who commissioned it.

Of course, Rocher is putting the heat on Laforge. Rocher got himself added to the Groovy despotry 3 years ago, even though he doesn't contribute to Groovy in any way, intending to take it over when he can. For the Grails Exchange in London (Dec 2012), the initial speaking schedule showed Rocher and Laforge speaking at the same time in different rooms. Laforge had to fight to get an exclusive timeslot, knowing no-one would attend his talks if there was a Grales one at the same time. With the vert.x hijack, Rocher is again showing Laforge who's in charge. If Laforge doesn't meet his targets, he's out of VMWare and out of Groovy.

Rocher's also slugging it to me: I am one of those he replied to in the email. But there's a key difference between vert.x and the Groovy Language. Tim Fox initiated vert.x while he was an employee of VMWare, but Groovy was initiated by its creator James Strachan before VMWare, EMC, SpringSource, G2One, Laforge, or Rocher had any involvement. When Strachan handed on the groovy baton for Groovy, Jochen Theodorou took over the tech lead role, Laforge took over the managerial title, and I took over the brand ownership.

Only those who have done actual coding and testing have a claim to be called a developer of Groovy, e.g. Jochen Theodorou, Paul King, Cedric Champeau, Roshan Dawrani, Alex Tkachman, Jeremy Rayner, Sam Pullara. Only those who have managed properly have a claim to be called a project manager of Groovy, and Laforge fails in this regard, having sold out to corporate thugs VMWare and Rocher. And only I have a claim to be called brand owner of Groovy, having stood up to Rocher and made sure the Groovy Language keeps its groovy name.


30 November 2012

Groovy's Hijack, Deceive, and Flip

Rocher and his ilk have taken to talking about "Grover's endgame", likening me to a TV show serial killer devolving to some predetermined spectacle. But he's only trying to deflect attention away from himself and his own endgame, far more evil and sinister than anything I would want to play. Wolves like Rocher don't change their teeth, so to see what he's up to we only need look at what he's already done.

No sooner had Laforge hijacked Groovy from Strachan and begun remolding it to look like Ruby, he went looking for a co-conspirator to finish the job and build a clone of Rails, to skim off consulting and conference revenues from IT shops that can be bought off with sound-alike clones. Rocher greedily jumped at the chance to join him to recruit and manage a rotation of sucker open-source programmers to build it, and create a Potekim village of users. They started a company, flipped it as quick as possible to SpringSource, then again to VMWare. Hijack some BSD-licensed technology, deceive some programmers and users, then flip some companies for quick gains. Rocher's M.O. is hijack, deceive, and flip.

Rocher presents like he's tailman to Spring gurus Adrian Colyer, Juergen Hoeller, and Mark Pollack, but don't be fooled. He's already knifed Laforge, and he's going after these three next, to turn Spring into a core part of Grails, redefining VMWare's SpringSource division around Grails. He's no doubt already set up his sellout vehicles, perhaps contractual bonuses from VMWare or shares in Gradleware. He's been padding up Grails to be a distribution channel for well-known Java-based open-source software, like Hibernate and SiteMesh. Even AspectJ is in there, a stab at Colyer. Because Gradle builds Grails, he's pitching Gradleware as an essential property in any selloff of SpringSource, and using the bloated Gradle install as another distribution channel over more open-source software.

By keeping Grales and Gradle separate, he's keeping control by dividing, and covering himself if he gets found out at VMWare. Yes, he's probably already silently sabotaging their other business divisions, to make selling SpringSource look like a viable way to cover their losses by getting quick cash. He's already courting contacts at places like Oracle and JBoss, driving up the opening offers, ready to flip SpringSource and Gradleware for another quick payoff. Once again, hijack the Spring Framework, deceive developers and users about the popularity of Groovy and commercial commitment to Grails, then flip, betraying all stakeholders.

The payoffs from this evil endgame is why Rocher's been spreading vile about me, stirring up Australians and Chinese alike. While presenting a "professional face" in business and academic circles, he's playing another sinister hand behind the scenes, including surveilling me and my computer activities. Anyone associated with the Grails/Gradle echo-system needs to know, you WILL be betrayed. They're selling the idea of using or developing for Grails with the promise of later profit: that profit is NEVER coming because it'll end up in Rocher's pocket.


8 August 2012

Laforge "creates" another DSL

Laforge, in a mailing-list reply today (8 Aug 2012) to Russel Winder, claimed to "create" a query DSL for Gaelyk. In his example, he used the SELECT, SORT, and WHERE statements, but not the GROUP BY statement. On 25 Sep 2006 at 3:17pm, he claimed to "invent" such a groupBy method, both soliciting feedback on the mailing list and opening and closing a Jira request, all within the space of 4 minutes, giving no-one time to comment.

Of course, Laforge never invented anything. He'd copied it all from the Jira request I'd made 4 months earlier. Because it was my first ever Jira request, I neglected to format the code with the correct tags, and Groovy's Jira settings at that time didn't enable me to re-edit my request.

Instead of accepting my Jira request with corrected formatting, and encouraging me to continue contributing to Groovy, Laforge (and Rocher) gave me the "silent treatment", copying the useful stuff I posted and passing it off as their own. Instead of commenting that there was too much test data, Laforge ignored my Jira and made a snide remark about his own being the "perlishest". Although I didn't know it was them at the time, their behavior turned into nasty backtalk and outright harrassment over the following 3 years.

In March 2009, they changed tack. Laforge emailed me privately trolling for someone to work on GParsec, a project he'd just taken over the despotry of from Ken Barclay. Would you do work for someone who'd been ignoring, ridiculing, and slagging you for 3 years? If I had, Laforge today would be claiming to have "created" and "invented" more than a query DSL for Gaelyk.

I suspect the full extent of Laforge's "creation" of a DSL for Gaelyk involves translating Google-supplied sample code from Java to Groovy, removing some parentheses and dots to make use of the Groovy Antlr fixes Lidia Donaj put in 2 years ago, and pushing them to Github courtesy of the conversion done by Matthew McCullough 1 year ago. And if his DSL even has a GROUP BY statement, it's courtesy of my own Jira request 6 years ago. Laforge created nothing.

17 August update:

Laforge wrote in reply: "No group by on Google App Engine's datastore. So i haven't implemented that in that DSL.". Seems Laforge only translated Google's examples when writing Gaelyk, delivering as little as possible as late as possible, just enough to claim he'd written a Gaelyk DSL.

Laforge's more recent attacks against me include makign small changes into the AST-checking in Groovy 1.7 and 1.8 so my code samples stopped working, e.g. removing standalone try-statements. Last year, he and Rocher replaced Groovy++ with their own bundled clone so my GRegexes were no longer of any use. And they've been stonewalling my attempt to write a spec for Groovy, so I can reboot Groovy atop Clojure.

Laforge is a mere agent for Rocher, who hijacked Groovy to be nothing more than a part of Grales. He then did the same with Spring, and is now in a fighting match with Adrian Colyer to take over control of the Spring Framework, turning VMWare's SpringSource division into a Grales division, and promising VMWare's new management he can also take over Hibernate, perhaps even deliver all of JBoss to VMWare. He'll probably succeed against Colyer because he shares EMC/VMWare's mentality: get others to write the code for free under an onerous licence, then squeeze the users dry with consulting and conference fees. Grails and Spring users watch out: Rocher's out to get you.


















Posts removed because they've been superceded.

See earlier entries

Last edited Apr 8 at 6:45 AM by gavingrover, version 35

Comments

No comments yet.