grrrveeyoooo.gif

Gavin Grover's GROOVY Wikiblog

Rebuilding the Groovy Language from scratch, replacing Apache Groovy as the reference implementation, and promoting Unicode in programming.

Grolang, Groo(lang), and Vy

The Gro language and Groo plugin are the latest exciting additions to the Groovy ecosystem, integrating Unihan into the syntax.
  • Grolang 0.5 Release Notes on 20 October 2016 explains the motivations behind implemented features of Grolang
  • Go 1.7, Gro 0.4.0, & Groo on 25 August 2016 details how Grolang has split into Gro and Groo, and their move to a new github address
  • Go keywords on 26 September 2016 shows how it's feasible to eliminate all 25 keywords from Go
  • Qu's easy-to-remember rules in early 2016 shows the mapping between identifier names in Go and Gro
  • Qu 0.3 in early 2016 announces another component in the Groovy rebuild
  • kern & thomp in early 2016 adds thomp to other components of Grolang, such as kern and utf88
  • Identifier names in Gro in August 2015 shows the four categories of identifier names in Grolang, each cleanly matching to the language semantics
  • Spaceless Programming with Gro 0.3 in early 2015 shows how programming in Gro means never using spaces in language syntax again
  • Gro Precedences in early 2015 gives the precedence hierarchy for Groo's operators and punctuation
  • Gro's Quints and Runexes in early 2015 gives details about 2 oddly-named features of Groo
  • Gro begun in early 2015 announces the release of version 0.1 of Grolang, a Groovy rebuild built atop the Go 1.x platform
  • Groovy rebuild progresses in early 2015 isolates a single month (November 2003) when three separate but intertwined attacks hit the world of programming

Extending Unicode

Extending Unicode back to the 2.1 billion codepoints as originally specified by Pike and Thompson, but clipped down to 1 million in 2003.
  • 2048 volumes of GroovyCode on 4 May 2014 defines a Unicode volume to be 16 consecutive planes, and shows a possible assignment for them
  • GroovyCode's embedded 6-bit language: Ultracode on 31 May 2014 outlines ideas for a 64-token language embedded within Unicode's UTF-8 encoding
  • Introducing GroovyCode... on 28 March 2014 lists various facilities still lacking in Unicode for it to be of use in a programming language like Real Groovy
  • Unicode Ultra Normal Forms on 27 March 2014 describes the two new normal forms that UTF-88 needs if it's to be fully implemented
  • Groovy Unicode UTF-8-Ultra on 9 March 2014 explains how the present UTF-8 can define the 1 million codepoints originally specified by Pike and Thompson by using the top 2 private use planes as ultra-surrogates, which has since been implemented as UTF-88
  • The Groovy Future of Unicode on 11 January 2014 details how Unicode could extend UTF-16, give over 280 trillion codepoints in UTF-8, and define a 6-bit embedded language
  • The Groovy History of Unicode on 6 January 2014 details Unicode's rise from its beginnings as ASCII
  • Unicode Pattern Syntax Tokens on 6 February 2013 looks at the suitability of Unicode's Pattern Syntax tokens for operators and punctuation in Real Groovy
  • Kanji meets Programming on 24 August 2011 explains my motivation for integrating Unicode into Real Groovy
  • F.A.Q

Apache Groovy

Apache's stated ideals are good, but the way they're put into practise for the former Codehaus Groovy is bad.
  • The Road to Groovy's Manifesto on 26 November 2016 details events along the way that led up to my issuing the Groovist Manifesto early last year
  • Groovist Manifesto: Oct/Nov 2016 update logs progress to date on achieving the 3 aims of Groovy's manisfesto, including showing Rocher's latest tactic to fork Groovy for Grails
  • Groovy's TIOBE Fraud on 10 October 2016 shows how some grossly exaggerated figures reported by a small number of search engines is responsible for Groovy's distorted presence in the TIOBE Top 20
  • Purify Groovy's PMC on 2 October 2016 shows how only 44% of those in the Apache Groovy Project Management Committee have any history of participating in Groovy as shown by Github commits or Jira changes in the previous 18 months since joining the ASF
  • Apache Groovy's continuing fabrications in May 2016 questions whether any aspect of the download figures for Groovy claimed by its Apache overlords resembles the truth
  • Groovy's Governance in April 2106, and updated in October, reveals Laforge's tactics for maintaining his control over Groovy's committers and codebase
  • Volatile Groovy in February 2016 explains how Groovy's recent artificial rise in TIOBE is bad for the language and the ecosystem
  • Building up Groovy in January 2016 details 12 lies being spread around concerning the Groovy ecosystem
  • Inverted Groovy in late 2015 shows how Groovy's most widely distributed bundling product uses the tiniest amount of its features, whereas the use case utilizing the greatest variety of Groovy's features has virtually no-one using it
  • Groovy's Apache Hoax in October 2015 show how someone's creating a false narrative that Groovy joining the ASF has caused Groovy downloads to spike
  • Groovy Manifesto: Layering, Groovy Manifesto: updated, and Groovy's Manifesto: The Struggle Continues detail subsequent progress on achieving the goals of the manifesto
  • A Groovist Manifesto in March 2015 states Groovy implementations should be led by their technical people, applications using Groovy should not dictate its direction, and Groovy should be standardized for its various implementations

Pre-manifesto Groovy

When Groovy lost its financial support and couldn't find a replacement, I stepped up and issued the Groovist Manifesto.
  • Groovy's Cyberbully on 11 November 2014 summarizes the events that caused me to issue the Groovist Manifesto
  • Groovy's Gross Exaggerations on 10 May 2014 shows how someone had fabricated over half a million downloads of Groovy in a month
  • Groovy's Lies and Statistics on 27 January 2014 shows how someone has been promoting their own name on Groovy's Wikipedia site at the expense of the other despots, and how the surge in Groovy's popularity has been fabricated, both in the Tiobe Index and in the download stats
  • A Groovy Syntax Curse on 19 January 2014 explains why I always return to the Groovy Language
  • Clojure Vocab, Grojure Grammar on 30 November 2013 explains how Grojure attempts to ease cognitive overload by reducing the number of alphabetic names
  • Groovy continues on 16 November 2013 claims "someone" wasn't happy with just owning the org.codehaus.groovy implementation of Groovy, but was using corporate attorneys in their plot to steal ownership of the Groovy Language brand
  • Groovy's Coterie of Sociopaths on 11 November 2013 exposes an interconnected coterie of Sociopaths extending to Australia and China, and north and south California, with a Master Sociopath controlling it, perhaps someone directly associated with the American NSA, or maybe just some self-important Australian bureaucrat sitting at the end of their international feed
  • GrŐȌvy Timeline Updated, GrŐȌvy Timeline, and A GrȎŎvy Decade summarizes how Laforge knifed Strachan to take over the Groovy Language, and how Rocher had later knifed Laforge
  • Groovy's Laundry on 21 June 2013 shows how the traits announced for Groovy 2.2 had already been implemented 2 years previously in Groovy++ by Tkachman, and how Laforge and Rocher had conspired to launder those traits, announce a Documentation Effort as damage control, and indefinitely delay the MOP rewrite, Antlr grammar upgrade, and JDK8 lambda retrofit, all within 24 hours of the Dr Dobbs Groovy Conundrum analysis
  • Groovy's 100 roadmaps on 15 June 2013 shows how no progress had been made on Groovy 3's new MOP, Antlr 4 grammar, and retrofitted Java 8 lambdas in the previous year
  • Grails Deception on 4 June 2013 exposes how Rocher had spun a cover story for turning Grails into a distribution channel for SpringSource software only, while dropping everything significant not controlled by SpringSource such as Hibernate
  • Grȫȫvy ecosystem busts free! on 19 May 2013 suggests Laforge's need to define explicitly what software makes up an ecosystem is exactly why Groovy failed under his "commandership" in the first place
  • CRIMEAn Computing with Groovy on 30 March 2013 explains my strategy for integrating Unicode into the Groovy language rebuild
  • Attacks against Groovy on 27 March 2013 exposes how Rocher attacked me through linked proxies: Grails developers, the Australia/NZ residential property system, and the Chinese education industry
  • Groovy Debates on 16 March 2013 uses some equally-spaced incidents as isolated examples of what had been happening to me
  • Groovy Tweetroll from 23 February to 16 March 2013 shows how Groovy's "lines changed" footprint on Github didn't match up with its other footprints that weren't being measured by the Corger's popularity ranking
  • Groovy Buzzwords on 13 February 2013 questions Laforge's claims about Groovy's maturity, popularity, speed, stability, flexibility, readability, feature-set, and ecosystem
  • Groovy Confusion on 7 February 2013 claims Rocher was cancelling the MOP for Groovy 3, just like he did for Groovy 2, despite Theodorou getting 90 replies to a thread he'd begun about it
  • Groovy's thug steals another project on 11 January 2013 exposes how Rocher had shown unusual interest in Vert.x 3 weeks before VMware's lawyers turned up on Tim Fox's door in person during Christmas vacation demanding he "give up all administrative rights of the Vert.x GitHub project, Google group, vertx.io domain and Vert.x blog", and that Rocher was probably the corporate hitman who commissioned it
  • Groovy Visions Revisited on 5 January 2013, like the original Groovy Visions, claims Laforge bore responsibility for Groovy's continuing decline, second only to Rocher, and suggests they were claiming my exposure of the deceit surrounding Groovy had been responsible for that decline
  • Groovy slipping down the pole on 3 January 2013 suggests any claims that Groovy is climbing up a pole were fabricated
  • Frauds in Suits (Q & A) on 3 January 2013 answers some questions, such as a claim that 90% of my blog posts were only personal attacks against people behind Groovy and Grails, I replied it was important to expose the truth about Rocher and Laforge's true intentions for Groovy

The Road to Groovy 2.x

Instead of taking the crap slung my way by anonymous cowards, I exposed it all under my own name.
  • Groovy 2.0 finally released after 5 alphas, 8 betas, and 2 duds on 22 December 2012 suggests Groovy 2's real release was when is was shipped as part of Grails 2.2, and that Groovy 2's standalone release 6 months earlier had really been an extended beta-test for suckers who believed Rocher's lie that Groovy had any real intended use outside of Grails
  • Groovy Gearchange on 15 December 2012 suggests that software development teams shouldn't have non-technical people programming in them, and certainly not leading them, especially if the software being developed is a programming language
  • The Groovedral and the Ruby Bazaar on 8 December 2012 suggests Laforge fashioned Groovy to be an imitation of only Ruby, including cloning Ruby's extension methods, and it and Grails's primary purpose is to chisel consulting fees away from those considering using Ruby on Rails
  • Groovy's Hijack, Deceive, and Flip on 30 November 2012 suggests Rocher's M.O. was to hijack some open source technology, deceive some programmers and users, then flip some companies for quick gains
  • Groovy's Scheming on 9 November 2012 accuses Rocher and Laforge of tricking volunteers into using the Apache 2.0 license, then when the work's almost finished stirring up arguments among them to give themselves a public excuse to clone the work and bundle it with Groovy, under their own control
  • Promote Groovy, make it international on 25 October 2012 accuses Laforge of using talks he'd been giving to promote himself instead of the Groovy Language
  • Groovy 2012 F.A.Q on 15 September 2012 accuses Laforge of gaming Stack Overflow and Github to fabricate popularity for Groovy in the Redmonk programming language ranking, and of introducing the Elvis op name to fabricate less controversial origins for the G-String name rather than having fun with GrΦΦvy
  • Groovy grinds to a halt on 14 September 2012 suggests the Groovy despots didn't want any software not under SpringSource control in Groovy, and use the Groovy Help on Improvements, onerous SpringSource contributors agreement, and AST transformation annotation interface to get others to do all the development work on Groovy for free, then launder their code
  • Groovy's "echo-system" on 26 Augush 2012 asks why Grails and Gradle didn't bundle Groovy 2.0, and mentions how whereas Rails was built atop Ruby but doesn't try to control it, Grails had taken control of Groovy and was after Spring next
  • Groovy Language Spec on 17 August 2012 shows how Rocher and Laforge had been actively working against Groovy being spec'd, not wanting any competition to their own implementation of Groovy, and had even cynically used the JSR spec as titles in their signatures to fool others regarding their credibility
  • Laforge "creates" another DSL on 8 August 2012 shows how Laforge had passed off my very first feature request for Groovy as his own, and along with Rocher had given me the "silent treatment" for 3 years
  • Groovy "fights back" on 25 July 2012 accuses Laforge of suddenly U-turning on his marketing of Groovy 2.0 by suddenly reviving the two-release-old version 1.7 because almost no-one downloaded Groovy 2.0
  • Groovy ecosystem betrayals on 17 July 2012 suggests Rocher was rounding up Dierk Koenig, Andres Almiray, and Champeau to move against Laforge, and was after Rod Johnson's then vacant job
  • Groovy's desperate despotry on 13 July 2012 asks why Rocher became a Groovy despot a year previously when he contributed nothing to Groovy development, and why Codehaus rep Ben Walding had recently became a despot despite not being in any other Codehaus despotry
  • Groovy's Broken Closures on 5 July 2012 accuses Laforge of stirring up arguments at DecCon 2 to wear down and get rid of Groovy creator Strachan, and that's why Groovy's closures are broken
  • "Groovy Won"?, Promoting Groovy 2, and Groovy 3 set of posts in late June 2012 exposes many deceits and false claims surrounding the release of Groovy 2
  • Groovy 2.0.0 imminent on 15 June 2012 accuses Laforge of selling out Codehaus Groovy to EMC/VMWare in return for a more compliant funded worker, of changing the JSR 241 status to Dormant because they were unwilling to meet Oracle's transparency requirements, of making many marketing claims that can't be proven, of often silently removing features from Groovy, and of making tightly-controlled Groovy products look like a diversified ecosystem
  • Groovy Mars Rover on 29 April 2012 points out 18 bugs in some powerpoint slides Laforge had just posted about Groovy DSL's, and suggested he had neither any aptitude for coding nor enough discipline to test properly
  • Groovy Bait-and-Switch on 23 April 2012 accuses Laforge of trying to get 2 speaking slots in the 2012 Gr8te conference by promising another speaker then switching to himself at the last moment, and again accused Rocher of trying to kick Laforge out
  • Stagnant Groovy steals static code on 10 April 2012 shows how Groovy is ranked as a minor language in the O'Reilly hard copy book sales ranking, the least able to be gamed
  • Groovy and Gr8te differences on 5 March 2012 accuses Laforge of using the then 8 year old inactive JSR 241 for nothing more than giving himself an authoritative title to fool others, and that anyone who cared about the real Groovy ecosystem would encourage other implementations, just as there were of Python and Ruby
  • Grojure v0.2 Released on 27 Feb 2012 accuses Rocher of not contributing to Groovy for the previous 5 years, but keeping as much control as he can over Groovy because he was building a business empire based on Grails consulting
  • Groovy Reborn on 26 Dec 2011 accuses Laforge of being a "manager/recruiter fraud" who snuck in and stirred up arguments at Groovy's DevCon 2 in December 2005
  • Fake Groovy Exposed on 22 Nov 2011 said Groovy was a cathedral in a bazaar's clothing to fool the mort masses, its only purpose to milk profits from corporate IT shops, and its decline being hidden by the Codehaus cartel to prolong the gravy train
  • The Sociopath, the Clueless, and the Loser on 12 November 2011 calls Rocher a Sociopath, Laforge a Clueless, and Theodorou a Loser like me
  • Groovy's decline continues on 17 September 2011 accuses Laforge of badly promoting Groovy, saying it looked like he was trying to flog a gimmicky product by placing it between quality ones
  • Arabic, Chinese, and English aced for Groovy's scripts on 12 March 2011 claims neither was the Codehaus version of Groovy 1.x internationalized, nor did its developers intend to bother with it
  • The Rise and Fall of the Groovy Language on 23 January 2011 identifies 3 causes for Groovy's decline, viz, Groovy development had switched from being improved to extracting profit, Groovy's design and development was tied closely to Grails, and Groovy was a tightly-run cathedral posing as a bazaar, and anyone who didn't toe the line was out
  • A set of tutorials for Java newbies learning Groovy 1.7, copied from the ones hosted at the Codehaus Groovy documentation site from 2008 to 2015

Other Stuff

My blog entries have now been fully rearranged, and those referring to abandoned technical directions deleted, though those deleted posts can be seen in the featured download above.

CJK Decomposition

My previous little project was creating the CJK decomposition data file, a graphical analysis of the approx 75,000 Chinese/Japanese characters in Unicode.

Modelling a programming language on a natural language

These are older entries, mainly from my gavingrover.blogspot.com site.

Last edited Nov 26 at 8:42 AM by gavingrover, version 73