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.
  • Gro 0.7 is released, the Groovist Manifesto has been updated, and Real Groovy is moving from
  • Groovy Japandarin on 23 August 2017 explains how Groo(lang) uses both Chinese and Japanese simplified Han characters
  • 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

Unicode and Unicode-Ultra

Extending Unicode back to the 2.1 billion codepoints as originally specified by Pike and Thompson, but clipped down to 1 million in 2003.

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

Last edited Oct 16 at 4:16 AM by gavingrover, version 89