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.
  • Groovy shazam! on 6 May 2017 unveils the logos for Groo(lang) and Vy
  • Go Symbology on 17 February 2017 lists all symbols used by Go's many little languages
  • Designing Gro on 16 January 2017 explains why Gro uses Unihan the way it does
  • Go keywords updated on 17 December 2016 shows how it's feasible to eliminate all 25 keywords from Go
  • 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

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.
  • Expanding Unicode, 2017 F.A.Q from 26 Jan 2017 answers questions about topics related to expanding Unicode, such as utf-88
  • 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.
  • ASF's devious plans for Apache Groovy on 2 February 2017 questions whether the ASF and Google are colluding to promote Apache Groovy in TIOBE
  • 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 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
These next 2 posts help show why article 2 of the Groovist Manifesto (Groovy's governance should be independent of the applications that use it) is needed:
  • 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, domain and Vert.x blog", and that Rocher was probably the corporate hitman who commissioned it
  • 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
These next 2 posts help show why article 1 of the Groovist Manifesto (Groovy implementations should be led by their technical people) is needed:
  • 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'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
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

Last edited May 6 at 6:18 AM by gavingrover, version 84