galaaz 2.1.4 → 2.1.5

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 03ba582ba7054d11d6ce78bd5bf50fc424aac1a391209dee52749dd6bb642677
-  data.tar.gz: a9997f60ab4446b6ecdbda2cfa32a1f9de03fb002b8d2bdc5df945043fe547ab
+  metadata.gz: d39a98e695448ffb0166d33746445cc0076efcbd15e6f34250c99512e7c8e71d
+  data.tar.gz: eff6228e3febeb502838f1a6b99e38d03186327678b1a5535e58e8548e516d72
 SHA512:
-  metadata.gz: fcbc2a6d680c73df54768ff9a623d11f3c4723f030416f8d0937183fef4247b66982aa5bc7c0600d97ade5b9a67e7a6b17eecd7c8e7f507d0528510086fd33db
-  data.tar.gz: fa9b17e4e135ea1a199b76103f5f86739312816dee9e3fae332fa9e0773b6eb80124bd1f37a65759afdd610bc5a7fb9d4eba2c928c08adfd730aaf37f17899b8
+  metadata.gz: ffe309c54323c08acabe1752c677cd67090878170b33853eb739195f4be36450379b2e100dc5e9ecfa317e4e4373aed8082dfee8407bb5231cd1d5b41c6fbdf2
+  data.tar.gz: daef47d66a2f3c20e2e430797ffd6193e9d80cde6ffc9b82856835dab4c0a3e3f8833b17d1b6b3389e4e5e3c5a7cccba8aee42d9b023b2e110758b6e678e9a2c

data/CHANGELOG.md

@@ -1,5 +1,23 @@
 # Changelog
 
+## 2.1.5
+
+### Fixed
+
+- `gknit` / `gknit_Rscript`: resolve input with `File.expand_path` so absolute paths
+  (e.g. `~/galaaz-blogs/...`) are not prefixed with `Dir.pwd` (broke when run from
+  `~/.local/bin`).
+- `galaaz add ledger`: do not strip app Ruby version pins; keep engine-agnostic
+  RubyGems `gem "galaaz"` rewrites only.
+
+### Changed
+
+- Omarchy `omarchy-galaaz-add`: install pandoc via `pandoc-bin` or the latest GitHub
+  linux binary into `~/.local/bin` — not Arch `pandoc` / `pandoc-cli` (Haskell deps).
+- Omarchy menu Docs / GitHub rows use `omarchy-launch-webapp` (same as Omarchy Learn).
+- `galaaz add arrow` / ledger path: prefer Apache `LIBARROW_BINARY` prebuilt libarrow
+  (avoid Arch pacman arrow version skew on Omarchy).
+
 ## 2.1.4
 
 ### Added

data/README.md

@@ -2,7 +2,7 @@
 title: "Galaaz Manual"
 subtitle: "R-on-Rails: GNU R meets Ruby for the web"
 author: "Rodrigo Botafogo"
-tags: [Galaaz, "R-on-Rails", Ruby, Rails, JRuby, R, "GNU R", ggplot2, knitr, dplyr, Bioconductor, Arrow]
+tags: [Galaaz, "R-on-Rails", Ruby, Rails, JRuby, CRuby, R, "GNU R", ggplot2, knitr, dplyr, Bioconductor, Arrow]
 date: "2026"
 bibliography: "../../examples/Bibliography/stats.bib"
 output:
@@ -358,7 +358,13 @@ A **table of all `bin/` scripts** (bootstrap, Ruby launcher, gstudio, gknit, tes
    **`bin/run_all_rspec`** (same `GALAAZ_RUBY` rule). **`bin/galaaz-jruby`** remains a thin
    wrapper that forces JRuby.
 
-A **gstudio** try image (JRuby + R + Galaaz already installed) is **`docker run --rm -it ghcr.io/rbotafogo/galaaz-try:gstudio`** (or **`./docker/try-gstudio/run.sh`** from a checkout). Maintainers can prove a RubyGems install on a throwaway Ubuntu machine (no repo inside the container) with **`./docker/cold-install/run.sh published-specs`** (JRuby) or **`./docker/cold-install-cruby/run.sh published-specs`** (CRuby).
+A **gstudio** try image with Galaaz already installed is available for both engines:
+**JRuby** — `docker run --rm -it ghcr.io/rbotafogo/galaaz-try:gstudio` (or
+`./docker/try-gstudio/run.sh` from a checkout); **CRuby** —
+`docker run --rm -it ghcr.io/rbotafogo/galaaz-try:cruby` (or `./docker/try-cruby/run.sh`).
+Maintainers can prove a RubyGems install on a throwaway Ubuntu machine (no repo inside
+the container) with `./docker/cold-install/run.sh published-specs` (JRuby) or
+`./docker/cold-install-cruby/run.sh published-specs` (CRuby).
 
 ## Windows + WSL2 (optional: Docker / R in a container)
 
@@ -394,11 +400,18 @@ WSL integration is enabled for the distro where Galaaz is installed.
 ``` ruby
   vec = R.c(1, 2, 3, 4)
   puts vec
+
+  # R.foo(...) calls an R *function*. Datasets are objects — fetch with ~:
+  df = ~R[:mtcars]
+  puts R.summary(df)
 ```
 
 ```
 ## [1] 1 2 3 4
 ```
+
+(`R.mtcars` is wrong: it becomes `mtcars()` in R and fails. With
+`using Galaaz::SymbolDSL`, the short form `~:mtcars` also works.)
   
 * Run all specs
 
@@ -4261,10 +4274,11 @@ pulls in several dependencies; the first install can take several minutes.
 ## Example: DESeq2 on the airway dataset
 
 The script **`examples/bioconductor_deseq2_airway/deseq2_airway_galaaz.rb`** is the canonical
-version in the repository. Run it from the **Galaaz repository root** with JRuby, for example:
+version in the repository. Run it from the **Galaaz repository root** with either engine, for example:
 
 ```text
-bin/galaaz-jruby examples/bioconductor_deseq2_airway/deseq2_airway_galaaz.rb
+bin/galaaz-ruby examples/bioconductor_deseq2_airway/deseq2_airway_galaaz.rb
+# or: bin/galaaz-jruby examples/bioconductor_deseq2_airway/deseq2_airway_galaaz.rb
 ```
 
 The workflow in Ruby mirrors a standard DESeq2 vignette:
@@ -4293,7 +4307,7 @@ manual is knitted, because **DESeq2** is heavy and may be absent on the build ma
 
 ``` ruby
 # Canonical script: examples/bioconductor_deseq2_airway/deseq2_airway_galaaz.rb
-# Run: bin/galaaz-jruby examples/.../deseq2_airway_galaaz.rb (repo root).
+# Run: bin/galaaz-ruby examples/.../deseq2_airway_galaaz.rb (repo root).
 
 require 'galaaz'
 

data/bin/gknit

@@ -76,18 +76,11 @@ end
 remaining_args = parser.permute(ARGV.dup)
 ARGV.replace(remaining_args)
 
-# Sets the directory
-dir = Dir.pwd
-
-#=========================================================================================
-# Check if the name of the file to gKnit was given and that it exists. If not,
-# issue error.
-#=========================================================================================
-
 options[:input_file] = ARGV[0] if !ARGV[0].nil?
 raise "Input file name is required for gKnitting. Add -f FILE or --input_file FILE. For help, type gknit -h" if
   options[:input_file].nil?
-options[:input_file] = "#{dir}/#{options[:input_file]}"
+# File.expand_path keeps absolute paths intact (do not prefix Dir.pwd).
+options[:input_file] = File.expand_path(options[:input_file])
 raise "File #{options[:input_file]} does not exist!" if !File.exist?(options[:input_file])
 
 #=========================================================================================

data/bin/gknit_Rscript

@@ -30,9 +30,6 @@ OptionParser.new do |opts|
   end
 end.parse!
 
-# Sets the directory
-dir = Dir.pwd
-
 #=========================================================================================
 # Check if the name of the file to gKnit was given and that it exists. If not,
 # issue error.
@@ -41,7 +38,8 @@ dir = Dir.pwd
 options[:input_file] = ARGV[0] if !ARGV[0].nil?
 raise "Input file name is required for gKnitting. Add -f FILE or --input_file FILE. For help, type gknit -h" if
   options[:input_file].nil?
-options[:input_file] = "#{dir}/#{options[:input_file]}"
+# File.expand_path keeps absolute paths intact (do not prefix Dir.pwd).
+options[:input_file] = File.expand_path(options[:input_file])
 raise "File #{options[:input_file]} does not exist!" if !File.exist?(options[:input_file])
 
 #=========================================================================================

data/bin/gstudio_irb.rb

@@ -1,36 +1,85 @@
+# frozen_string_literal: true
+
 require 'galaaz'
 require 'ggplot'
-require 'irb/completion'
 require 'pp'
+require 'irb'
+require 'reline'
 
-IRB.conf[:PROMPT][:CUSTOM] = {
-  :PROMPT_I => "galaaz >> ",
-  :PROMPT_S => "%l>> ",
-  :PROMPT_C => ".. ",
-  :PROMPT_N => ".. ",
-  :RETURN => "=> %s\n"
-}
+# --- terminal capability -------------------------------------------------------
 
-IRB.conf[:PROMPT_MODE] = :CUSTOM
+def gstudio_colorize?
+  return false unless ENV['NO_COLOR'].to_s.empty?
+  return false if ENV['TERM'].to_s == 'dumb'
+  true
+end
+
+def gstudio_version
+  spec = Gem.loaded_specs['galaaz']
+  return spec.version.to_s if spec
+
+  version_rb = File.expand_path('../../version.rb', __FILE__)
+  if File.file?(version_rb)
+    load version_rb
+    return $version.to_s if defined?($version) && $version
+  end
+
+  '?'
+end
+
+colorize = gstudio_colorize?
+dumb = ENV['TERM'].to_s == 'dumb'
+
+# --- modern IRB defaults (Ruby >= 3.1 / Reline) --------------------------------
+
+IRB.conf[:USE_MULTILINE] = !dumb
+IRB.conf[:USE_COLORIZE] = colorize
+IRB.conf[:USE_AUTOCOMPLETE] = !dumb
 IRB.conf[:AUTO_INDENT] = true
 IRB.conf[:SAVE_HISTORY] = 1000
-IRB.conf[:HISTORY_FILE] = '~/.galaaz.history'
+IRB.conf[:HISTORY_FILE] = File.expand_path('~/.galaaz.history')
+# R-like session: expression results are printed by Galaaz/R, not Ruby inspect.
 IRB.conf[:ECHO] = false
 
-# history command
-def history(count = 0)
+cyan = colorize ? "\e[36m" : ''
+bold = colorize ? "\e[1m" : ''
+reset = colorize ? "\e[0m" : ''
+
+IRB.conf[:PROMPT][:CUSTOM] = {
+  PROMPT_I: "#{bold}#{cyan}galaaz#{reset} >> ",
+  PROMPT_S: '%l>> ',
+  PROMPT_C: '.. ',
+  PROMPT_N: '.. ',
+  RETURN: "=> %s\n"
+}
+IRB.conf[:PROMPT_MODE] = :CUSTOM
+
+prior_rc = IRB.conf[:IRB_RC]
+IRB.conf[:IRB_RC] = lambda do |context|
+  prior_rc.call(context) if prior_rc.respond_to?(:call)
+  puts "Galaaz #{gstudio_version} on #{RUBY_ENGINE} #{RUBY_VERSION} " \
+       "(IRB #{IRB::VERSION}). Tab completes; `history` lists input."
+end
 
-  # Get history into an array
-  history_array = Readline::HISTORY.to_a
+# --- session helpers -----------------------------------------------------------
 
-  # if count is > 0 we'll use it.
-  # otherwise set it to 0
-  count = count > 0 ? count : 0
+module Kernel
+  # Print recent input lines. Optional +count+ limits to the last N entries.
+  def history(count = 0)
+    history_array =
+      if defined?(Reline::HISTORY)
+        Reline::HISTORY.to_a
+      elsif defined?(Readline::HISTORY)
+        Readline::HISTORY.to_a
+      else
+        []
+      end
 
-  if count > 0
-    from = hist.length - count
-    history_array = history_array[from..-1] 
-  end
+    if count.is_a?(Integer) && count > 0
+      history_array = history_array.last(count)
+    end
 
-  print history_array.join("\n")
+    puts history_array.join("\n")
+    nil
+  end
 end

data/blogs/README.md

@@ -95,6 +95,6 @@ GALAAZ_DEBUG_R=1 bin/run_example examples/sthda_ggplot/all.rb
 
 ## Requirements
 
-- **JRuby** (same as specs/examples).
+- **JRuby** or **CRuby** (same as specs/examples; use `bin/galaaz-ruby` / `GALAAZ_RUBY`).
 - **R** with packages used by the document (e.g. `rmarkdown`, `knitr`, `ggplot2`).
 - Run from the project root so `lib` and `bin` resolve correctly.

data/blogs/galaaz_ggplot/galaaz_ggplot.Rmd

@@ -1,8 +1,8 @@
 ---
 title: "Ruby Plotting with Galaaz"
-subtitle: "An example of tightly coupling Ruby and R (JRuby + GNU R, Galaaz 2.0)"
+subtitle: "An example of tightly coupling Ruby and R (JRuby or CRuby + GNU R, Galaaz 2.0)"
 author: "Rodrigo Botafogo"
-tags: [Galaaz, Ruby, R, JRuby, "GNU R", ggplot2]
+tags: [Galaaz, Ruby, R, JRuby, CRuby, "GNU R", ggplot2]
 date: "16 October 2018 (narrative updated for Galaaz 2.0, 2026)"
 output:
   html_document:
@@ -36,11 +36,11 @@ widely used examples among **many thousands** of packages on PyPI for numerical
 With Galaaz we do not intend to re-implement any of the scientific libraries in R; we allow
 for very tight coupling between the two languages to the point that the Ruby developer does
 not need to think about R syntax for every call. **Galaaz 2.0** does this with **[JRuby](https://www.jruby.org/)**
-and **GNU R**: a **bridge** evaluates R from Ruby and exchanges data between processes.
+or **CRuby** and **GNU R**: a **bridge** evaluates R from Ruby and exchanges data between processes.
 
 An **earlier** Galaaz prototype used Oracle’s **GraalVM** with **TruffleRuby** and **FastR** in one JVM.
-That stack is **historical**; today’s documentation and tooling assume **JRuby + GNU R** (see the
-project manual and **`bin/galaaz-jruby`** / **`bin/gknit`**).
+That stack is **historical**; today’s documentation and tooling assume **NewBridge on JRuby or CRuby**
+(see the project manual and **`bin/galaaz-ruby`** / **`bin/gknit`**).
 
 For background on the old stack:
 
@@ -68,7 +68,7 @@ Galaaz is the Portuguese name for "Galahad".  From Wikipedia:
 
 ## Prerequisites (Galaaz 2.0)
 
-* **JRuby** and a compatible **JDK**
+* **JRuby** and a compatible **JDK**, *or* **CRuby 3.3+**
 * **GNU R** on your `PATH`
 
 The following R packages will be automatically installed when necessary, but could be installed prior
@@ -334,5 +334,5 @@ nicely complement R packages.
 
 For the Ruby developer, Galaaz allows the immediate use of R functions with minimal ceremony. As
 shown in the second example above, class `ScatterPlot` hides most R call details from the Ruby
-developer. **JRuby** provides **real parallel threads** on the Ruby side and access to the JVM
-ecosystem when you need it.
+developer. Prefer **JRuby** when you want **real parallel threads** on the Ruby side and access to
+the JVM ecosystem; **CRuby** works equally for the Galaaz bridge itself.

data/blogs/galaaz_ggplot/galaaz_ggplot.md

@@ -12,13 +12,13 @@ With Galaaz we do not intend to re-implement any of the scientific
 libraries in R; we allow for very tight coupling between the two
 languages to the point that the Ruby developer does not need to think
 about R syntax for every call. **Galaaz 2.0** does this with
-**[JRuby](https://www.jruby.org/)** and **GNU R**: a **bridge**
+**[JRuby](https://www.jruby.org/)** or **CRuby** and **GNU R**: a **bridge**
 evaluates R from Ruby and exchanges data between processes.
 
 An **earlier** Galaaz prototype used Oracle’s **GraalVM** with
 **TruffleRuby** and **FastR** in one JVM. That stack is **historical**;
-today’s documentation and tooling assume **JRuby + GNU R** (see the
-project manual and **`bin/galaaz-jruby`** / **`bin/gknit`**).
+today’s documentation and tooling assume **NewBridge on JRuby or CRuby**
+(see the project manual and **`bin/galaaz-ruby`** / **`bin/gknit`**).
 
 For background on the old stack:
 
@@ -47,7 +47,7 @@ Galaaz is the Portuguese name for “Galahad”. From Wikipedia:
 
 ## Prerequisites (Galaaz 2.0)
 
-- **JRuby** and a compatible **JDK**
+- **JRuby** and a compatible **JDK**, *or* **CRuby 3.3+**
 - **GNU R** on your `PATH`
 
 The following R packages will be automatically installed when necessary,
@@ -360,5 +360,5 @@ nicely complement R packages.
 For the Ruby developer, Galaaz allows the immediate use of R functions
 with minimal ceremony. As shown in the second example above, class
 `ScatterPlot` hides most R call details from the Ruby developer.
-**JRuby** provides **real parallel threads** on the Ruby side and access
-to the JVM ecosystem when you need it.
+Prefer **JRuby** when you want **real parallel threads** on the Ruby side and access
+to the JVM ecosystem; **CRuby** works equally for the Galaaz bridge itself.

data/blogs/gknit/gknit.Rmd

@@ -3,7 +3,7 @@ title: "How to do reproducible research in Ruby with gKnit"
 author:
     - "Rodrigo Botafogo"
     - "Daniel Mossé - University of Pittsburgh"
-tags: [Tech, Data Science, Ruby, R, JRuby, "GNU R", Galaaz, gKnit, knitr]
+tags: [Tech, Data Science, Ruby, R, JRuby, CRuby, "GNU R", Galaaz, gKnit, knitr]
 date: "29/04/2019 (narrative updated for Galaaz 2.0, 2026)"
 bibliography: stats.bib
 output:
@@ -109,7 +109,7 @@ written both in Ruby and/or R and output it in any of the available formats of _
 allows ruby developers to do literate programming and reproducible research by allowing them to
 have in a single document, text and code.
 
-gKnit runs with **JRuby**, **GNU R**, and **Galaaz** (the integration layer between Ruby and R—see below).
+gKnit runs with **JRuby or CRuby**, **GNU R**, and **Galaaz** (the integration layer between Ruby and R—see below).
 Knitr and **R Markdown** orchestrate the document; Galaaz’s engine keeps **Ruby state across chunks**
 and talks to R through the **bridge**. Ruby chunks can read and update R variables (`~R[:name]`, `R.*`)
 without GraalVM-style polyglot interop.
@@ -139,7 +139,7 @@ title: "How to do reproducible research in Ruby with gKnit"
 author: 
     - "Rodrigo Botafogo"
     - "Daniel Mossé - University of Pittsburgh"
-tags: [Tech, Data Science, Ruby, R, JRuby, "GNU R", Galaaz]
+tags: [Tech, Data Science, Ruby, R, JRuby, CRuby, "GNU R", Galaaz]
 date: "20/02/2019"
 output:
   html_document:
@@ -634,7 +634,7 @@ puts model.test.head
 gKnit also allows developers to document and load files that are not in the same directory
 of the '.Rmd' file.
 
-Here is an example of loading the 'find.rb' file from **JRuby** (via `$LOAD_PATH`). In this example, relative
+Here is an example of loading the 'find.rb' file from Ruby (via `$LOAD_PATH`). In this example, relative
 is set to FALSE, so Ruby will look for the file in its $LOAD\_PATH, and the user does not
 need to know its directory.
 
@@ -658,9 +658,9 @@ the Yaml header to generate this blog in PDF format instead of HTML:
 
 ```
 ---
-title: "gKnit - Ruby and R Knitting with Galaaz (JRuby + GNU R)"
+title: "gKnit - Ruby and R Knitting with Galaaz (JRuby or CRuby + GNU R)"
 author: "Rodrigo Botafogo"
-tags: [Galaaz, Ruby, R, JRuby, "GNU R", knitr, gknit]
+tags: [Galaaz, Ruby, R, JRuby, CRuby, "GNU R", knitr, gknit]
 date: "29 October 2018"
 output:
   pdf\_document:
@@ -683,13 +683,13 @@ be imported from files in the system.  Ideally, in reproducible research, all th
 needed to rebuild a report should be easily packed together (in the same zipped directory)
 and distributed to peers for reexecution.
 
-**Galaaz 2.0** pairs **JRuby** with **GNU R**: you keep the full CRAN/Bioconductor world in R while
+**Galaaz 2.0** pairs **JRuby or CRuby** with **GNU R**: you keep the full CRAN/Bioconductor world in R while
 writing orchestration, reuse, and application code in Ruby. The effort to wrap Ruby over R (Galaaz)
 and to wrap Knitr as gKnit was tiny compared to reimplementing R’s ecosystem in Ruby—much like
 Python’s investment in NumPy and Pandas, which no Ruby project is likely to duplicate.
 
 An **earlier** prototype used Oracle’s **GraalVM** and Truffle interop; the **current** stack is
-deliberately **standard GNU R** plus the Galaaz **bridge**, documented in the project manual.
+deliberately **standard GNU R** plus the Galaaz **bridge** on JRuby or CRuby, documented in the project manual.
 
 More interesting than wrapping the R libraries with Ruby, is that Ruby adds
 value to R, by allowing developers to use powerful and modern constructs for code reuse that
@@ -701,7 +701,7 @@ readability.
 
 ## Prerequisites (Galaaz 2.0)
 
-* **JRuby** and a compatible **JDK**
+* **JRuby** and a compatible **JDK**, *or* **CRuby 3.3+**
 * **GNU R** on your `PATH`
 
 The following R packages will be automatically installed when necessary, but could be installed prior
@@ -721,7 +721,7 @@ the usual build tools are typically enough.  On macOS, Xcode command-line tools
 ## Usage
 
 * **`bin/gknit`** \<filename\> (from the Galaaz repo or your install layout); use **`--output_format all`** for HTML and PDF together.
-* Run Ruby with **`bin/galaaz-jruby`** when you need the same JVM flags as the project (see the manual).
+* Run Ruby with **`bin/galaaz-ruby`** (either engine) or **`bin/galaaz-jruby`** when you need JRuby JVM flags (see the manual).
 
 
 # References

data/blogs/gknit/gknit.md

@@ -3,7 +3,7 @@ title: "How to do reproducible research in Ruby with gKnit"
 author:
     - "Rodrigo Botafogo"
     - "Daniel Mossé - University of Pittsburgh"
-tags: [Tech, Data Science, Ruby, R, JRuby, "GNU R", Galaaz, gKnit, knitr]
+tags: [Tech, Data Science, Ruby, R, JRuby, CRuby, "GNU R", Galaaz, gKnit, knitr]
 date: "29/04/2019 (narrative updated for Galaaz 2.0, 2026)"
 bibliography: stats.bib
 output:
@@ -133,7 +133,7 @@ written both in Ruby and/or R and output it in any of the available formats of _
 allows ruby developers to do literate programming and reproducible research by allowing them to
 have in a single document, text and code.
 
-gKnit runs with **JRuby**, **GNU R**, and **Galaaz** (the integration layer between Ruby and R—see below).
+gKnit runs with **JRuby or CRuby**, **GNU R**, and **Galaaz** (the integration layer between Ruby and R—see below).
 Knitr and **R Markdown** orchestrate the document; Galaaz’s engine keeps **Ruby state across chunks**
 and talks to R through the **bridge**. Ruby chunks can read and update R variables (`~R[:name]`, `R.*`)
 without GraalVM-style polyglot interop.
@@ -163,7 +163,7 @@ title: "How to do reproducible research in Ruby with gKnit"
 author: 
     - "Rodrigo Botafogo"
     - "Daniel Mossé - University of Pittsburgh"
-tags: [Tech, Data Science, Ruby, R, JRuby, "GNU R", Galaaz]
+tags: [Tech, Data Science, Ruby, R, JRuby, CRuby, "GNU R", Galaaz]
 date: "20/02/2019"
 output:
   html_document:
@@ -1246,7 +1246,7 @@ puts model.test.head
 gKnit also allows developers to document and load files that are not in the same directory
 of the '.Rmd' file.
 
-Here is an example of loading the 'find.rb' file from **JRuby** (via `$LOAD_PATH`). In this example, relative
+Here is an example of loading the 'find.rb' file from Ruby (via `$LOAD_PATH`). In this example, relative
 is set to FALSE, so Ruby will look for the file in its $LOAD\_PATH, and the user does not
 need to know its directory.
 
@@ -1361,9 +1361,9 @@ the Yaml header to generate this blog in PDF format instead of HTML:
 
 ```
 ---
-title: "gKnit - Ruby and R Knitting with Galaaz (JRuby + GNU R)"
+title: "gKnit - Ruby and R Knitting with Galaaz (JRuby or CRuby + GNU R)"
 author: "Rodrigo Botafogo"
-tags: [Galaaz, Ruby, R, JRuby, "GNU R", knitr, gknit]
+tags: [Galaaz, Ruby, R, JRuby, CRuby, "GNU R", knitr, gknit]
 date: "29 October 2018"
 output:
   pdf\_document:
@@ -1386,13 +1386,13 @@ be imported from files in the system.  Ideally, in reproducible research, all th
 needed to rebuild a report should be easily packed together (in the same zipped directory)
 and distributed to peers for reexecution.
 
-**Galaaz 2.0** pairs **JRuby** with **GNU R**: you keep the full CRAN/Bioconductor world in R while
+**Galaaz 2.0** pairs **JRuby or CRuby** with **GNU R**: you keep the full CRAN/Bioconductor world in R while
 writing orchestration, reuse, and application code in Ruby. The effort to wrap Ruby over R (Galaaz)
 and to wrap Knitr as gKnit was tiny compared to reimplementing R’s ecosystem in Ruby—much like
 Python’s investment in NumPy and Pandas, which no Ruby project is likely to duplicate.
 
 An **earlier** prototype used Oracle’s **GraalVM** and Truffle interop; the **current** stack is
-deliberately **standard GNU R** plus the Galaaz **bridge**, documented in the project manual.
+deliberately **standard GNU R** plus the Galaaz **bridge** on JRuby or CRuby, documented in the project manual.
 
 More interesting than wrapping the R libraries with Ruby, is that Ruby adds
 value to R, by allowing developers to use powerful and modern constructs for code reuse that
@@ -1404,7 +1404,7 @@ readability.
 
 ## Prerequisites (Galaaz 2.0)
 
-* **JRuby** and a compatible **JDK**
+* **JRuby** and a compatible **JDK**, *or* **CRuby 3.3+**
 * **GNU R** on your `PATH`
 
 The following R packages will be automatically installed when necessary, but could be installed prior
@@ -1424,7 +1424,7 @@ the usual build tools are typically enough.  On macOS, Xcode command-line tools
 ## Usage
 
 * **`bin/gknit`** \<filename\> (from the Galaaz repo or your install layout); use **`--output_format all`** for HTML and PDF together.
-* Run Ruby with **`bin/galaaz-jruby`** when you need the same JVM flags as the project (see the manual).
+* Run Ruby with **`bin/galaaz-ruby`** (either engine) or **`bin/galaaz-jruby`** when you need JRuby JVM flags (see the manual).
 
 
 # References

data/blogs/manual/manual.Rmd

@@ -2,7 +2,7 @@
 title: "Galaaz Manual"
 subtitle: "R-on-Rails: GNU R meets Ruby for the web"
 author: "Rodrigo Botafogo"
-tags: [Galaaz, "R-on-Rails", Ruby, Rails, JRuby, R, "GNU R", ggplot2, knitr, dplyr, Bioconductor, Arrow]
+tags: [Galaaz, "R-on-Rails", Ruby, Rails, JRuby, CRuby, R, "GNU R", ggplot2, knitr, dplyr, Bioconductor, Arrow]
 date: "2026"
 bibliography: "../../examples/Bibliography/stats.bib"
 output:
@@ -66,18 +66,20 @@ of libraries for data analysis.
 Until recently, there was no real perspective for Ruby to bridge this gap.
 Implementing a complete scientific computing infrastructure would take too long.
 
-**Galaaz 2.0** couples **JRuby** (Ruby on the JVM) with **GNU R**—the same R you use for
-CRAN and Bioconductor. Ruby and R run in **separate processes**; the **Galaaz bridge**
-sends requests to R and returns results to Ruby. From your point of view you still write
-Ruby: `R.c(...)`, `R.library('ggplot2')`, `~R[:mtcars]`, and dplyr-style chains on R objects.
-You do not need to learn R syntax to get a lot done, though reading R documentation for
-individual packages remains useful.
+**Galaaz 2.0** supports **JRuby** and **CRuby** equally for the same NewBridge protocol.
+Pick the Ruby that fits your app: JRuby when you want real multithreading for web and I/O;
+CRuby when you prefer MRI. R remains the same **GNU R** you use interactively—including
+compiled extensions and Bioconductor. Ruby and R run in **separate processes**; the
+**Galaaz bridge** sends requests to R and returns results to Ruby. From your point of view
+you still write Ruby: `R.c(...)`, `R.library('ggplot2')`, `~R[:mtcars]`, and dplyr-style
+chains on R objects. You do not need to learn R syntax to get a lot done, though reading R
+documentation for individual packages remains useful.
 
 Earlier experiments with Galaaz used Oracle’s **GraalVM** with TruffleRuby and FastR so that
 Ruby and R could share one runtime. That path is no longer the focus: **standard GNU R**
 gives full compatibility with the R package ecosystem (including compiled extensions and
-Bioconductor) while JRuby gives a mature Ruby with **real multithreading** for application
-and I/O code.
+Bioconductor) while either Ruby engine talks to R over NewBridge (JRuby for mature
+multithreading on the application side; CRuby when you prefer MRI).
 
 The bridge handles **communication and typing** between the two worlds; large tables can
 also flow through **Apache Arrow** on the R side when you use the optional helpers described
@@ -241,14 +243,16 @@ For day-to-day **2.0** use, rely on **`bin/galaaz-ruby`** (or **`bin/galaaz-jrub
 Typical development and CI targets:
 
 * **Linux** — recent Ubuntu LTS or comparable distributions (x86_64).
-* **macOS** — recent releases with JRuby and GNU R available.
+* **macOS** — recent releases with JRuby or CRuby and GNU R available.
 * **Windows** — use **WSL2** (same Linux stack as above); native Windows is not the primary target.
 
 The native **gatekeeper** component under `ext/new_bridge` is built with `make` and a C++ toolchain; see the project `README` if compilation fails on your platform.
 
 # Dependencies
 
-* **JRuby** — Galaaz 2.0 requires JRuby (tested with **10.1.1.0**) and a matching **JDK** (tested with **Java 21**). MRI Ruby is not supported.
+* **Ruby** — **JRuby** or **CRuby** (both supported for NewBridge). Tested with **JRuby 10.1.1.0**
+  (+ **JDK 21**) and **CRuby 3.3.12**. Use `bin/galaaz-ruby` (honors `GALAAZ_RUBY`) or plain
+  `gem install galaaz` under the Ruby you choose.
 * **GNU R** — `R` and `Rscript` on your `PATH` (tested with **4.3.3**), plus a C++ toolchain (`g++`, `make`) and the **Rcpp** package to compile the gatekeeper.
 * **galaaz gem** — runtime dependency `msgpack` is pulled in by `gem install`.
 * Optional: **Docker** — if you run R in a container (common on WSL2); see bootstrap below.
@@ -258,29 +262,40 @@ The native **gatekeeper** component under `ext/new_bridge` is built with `make`
 
 The supported install is **`gem install` + compile the gatekeeper**. You do not need a git clone.
 
-1. Install **JRuby**, a compatible **JDK**, and **GNU R** (with `Rscript` and a C++ compiler).
+1. Install **JRuby** (and a compatible **JDK**) **or CRuby 3.3+**, plus **GNU R** (with `Rscript` and a C++ compiler).
 2. In R, install **Rcpp**: `install.packages("Rcpp")`.
-3. Install the gem: `jruby -S gem install galaaz`
+3. Install the gem: `jruby -S gem install galaaz` (or `gem install galaaz` under CRuby).
 4. Compile the native gatekeeper from the installed gem:
 
    ```
-   gem_dir="$(jruby -e "puts Gem::Specification.find_by_name('galaaz').full_gem_path")"
+   gem_dir="$(ruby -e "puts Gem::Specification.find_by_name('galaaz').full_gem_path")"
+   # under JRuby: gem_dir="$(jruby -e "puts Gem::Specification.find_by_name('galaaz').full_gem_path")"
    make -C "${gem_dir}/ext/new_bridge" all
    ```
 
-5. Ensure **`R`** starts GNU R and can install packages (network access to CRAN when you first call `R.install_and_loads`). For **Apache Arrow** on Java 9+, pass `-J--add-opens=java.base/java.nio=ALL-UNNAMED` to JRuby (from a checkout, `bin/galaaz-jruby` does this).
+5. Ensure **`R`** starts GNU R and can install packages (network access to CRAN when you first call `R.install_and_loads`). For **Apache Arrow** on **JRuby** (Java 9+), the child JVM needs `--add-opens=java.base/java.nio=ALL-UNNAMED` via **`JAVA_OPTS`** (from a checkout, `bin/galaaz-jruby` and `mise.toml` set this; a leading `jruby -J... -S bundle exec` does **not** pass `-J` to rspec). On **CRuby**, install Apache Arrow GLib (`libarrow-glib-dev` from the [Apache Arrow APT](https://arrow.apache.org/install/) repo) and `gem install red-arrow` matching `pkg-config --modversion arrow-glib`. Do not install the unrelated Rubygems package named `arrow`.
 
 For **gKnit**, **knitr**, **rmarkdown**, and LaTeX (PDF output), install the corresponding R packages, **Pandoc**, and a TeX distribution if you need PDF; the repository includes helpers such as **`bin/install-tinytex`** where appropriate.
 
-A **table of all `bin/` scripts** (bootstrap, JRuby wrapper, gstudio, gknit, test runners, and which ones are legacy) is in the section **Command-line tools (`bin/`)** earlier in this manual.
+A **table of all `bin/` scripts** (bootstrap, Ruby launcher, gstudio, gknit, test runners, and which ones are legacy) is in the section **Command-line tools (`bin/`)** earlier in this manual.
 
 ### From a repository checkout (contributors)
 
-1. Install **bundler** if needed, then run **`jruby -S bundle install`** in the repository root.
+1. Install **bundler** if needed, then run **`bundle install`** with your chosen Ruby
+   (`jruby -S bundle install` or CRuby `bundle install`) in the repository root.
 2. Build the bridge native code: **`make -C ext/new_bridge all`** (or **`rake compile_gatekeeper`**).
-3. Run scripts with **`bin/galaaz-jruby`** (sources **`bin/galaaz_jruby_env.inc.sh`** and adds **`-I lib`**).
-
-A **gstudio** try image (JRuby + R + Galaaz already installed) is **`docker run --rm -it ghcr.io/rbotafogo/galaaz-try:gstudio`** (or **`./docker/try-gstudio/run.sh`** from a checkout). Maintainers can prove a RubyGems install on a throwaway Ubuntu machine (no repo inside the container) with **`./docker/cold-install/run.sh published-specs`**.
+3. Run scripts with **`bin/galaaz-ruby`** (uses `ruby` on `PATH`; set **`GALAAZ_RUBY=jruby`** or
+   **`GALAAZ_RUBY=ruby`** to force an engine). Spec runners: **`bin/run_rspec`** /
+   **`bin/run_all_rspec`** (same `GALAAZ_RUBY` rule). **`bin/galaaz-jruby`** remains a thin
+   wrapper that forces JRuby.
+
+A **gstudio** try image with Galaaz already installed is available for both engines:
+**JRuby** — `docker run --rm -it ghcr.io/rbotafogo/galaaz-try:gstudio` (or
+`./docker/try-gstudio/run.sh` from a checkout); **CRuby** —
+`docker run --rm -it ghcr.io/rbotafogo/galaaz-try:cruby` (or `./docker/try-cruby/run.sh`).
+Maintainers can prove a RubyGems install on a throwaway Ubuntu machine (no repo inside
+the container) with `./docker/cold-install/run.sh published-specs` (JRuby) or
+`./docker/cold-install-cruby/run.sh published-specs` (CRuby).
 
 ## Windows + WSL2 (optional: Docker / R in a container)
 
@@ -315,8 +330,15 @@ WSL integration is enabled for the distro where Galaaz is installed.
 ```{ruby simple_example}
   vec = R.c(1, 2, 3, 4)
   puts vec
+
+  # R.foo(...) calls an R *function*. Datasets are objects — fetch with ~:
+  df = ~R[:mtcars]
+  puts R.summary(df)
 ```
-  
+
+(`R.mtcars` is wrong: it becomes `mtcars()` in R and fails. With
+`using Galaaz::SymbolDSL`, the short form `~:mtcars` also works.)
+
 * Run all specs
 
   > galaaz specs:all
@@ -695,9 +717,9 @@ puts vec.map { |x| x + 2 }
 
 This manual has been formatted using gKnit.  gKnit uses knitr and R Markdown to knit 
 a document in Ruby or R and output it in any of the available formats for R Markdown.
-gKnit runs with **JRuby**, **GNU R**, and Galaaz.  In gKnit, Ruby variables are persisted between 
-chunks, making it an ideal solution for literate programming. Also, since it is based 
-on Galaaz, Ruby chunks can have access to R variables and combining Ruby with R in one 
+gKnit runs with **JRuby or CRuby**, **GNU R**, and Galaaz.  In gKnit, Ruby variables are persisted between
+chunks, making it an ideal solution for literate programming. Also, since it is based
+on Galaaz, Ruby chunks can have access to R variables and combining Ruby with R in one
 document is natural.
 
 The idea of "literate programming" was first introduced by Donald Knuth in the 
@@ -2071,7 +2093,8 @@ a real **Arrow `Table` inside GNU R**. From there you use R’s **`arrow`** and
 as usual: **`group_by`** on the Arrow table, **`summarise`** for aggregates, then **`collect()`** to
 materialize a tibble when you need in-memory R rows.
 
-That pattern matches production use: **JRuby threads** (or sequential code) assemble many rows in
+That pattern matches production use: **JRuby threads** or a **multi-process CRuby** app
+(or sequential code) assemble many rows in
 Ruby; you pay **one** bridge-heavy handoff to R; **dplyr** runs vectorised work on the Arrow table
 in R.
 
@@ -2175,10 +2198,11 @@ pulls in several dependencies; the first install can take several minutes.
 ## Example: DESeq2 on the airway dataset
 
 The script **`examples/bioconductor_deseq2_airway/deseq2_airway_galaaz.rb`** is the canonical
-version in the repository. Run it from the **Galaaz repository root** with JRuby, for example:
+version in the repository. Run it from the **Galaaz repository root** with either engine, for example:
 
 ```text
-bin/galaaz-jruby examples/bioconductor_deseq2_airway/deseq2_airway_galaaz.rb
+bin/galaaz-ruby examples/bioconductor_deseq2_airway/deseq2_airway_galaaz.rb
+# or: bin/galaaz-jruby examples/bioconductor_deseq2_airway/deseq2_airway_galaaz.rb
 ```
 
 The workflow in Ruby mirrors a standard DESeq2 vignette:
@@ -2206,7 +2230,7 @@ manual is knitted, because **DESeq2** is heavy and may be absent on the build ma
 
 ```{ruby deseq2_airway_full_listing, eval=FALSE}
 # Canonical script: examples/bioconductor_deseq2_airway/deseq2_airway_galaaz.rb
-# Run: bin/galaaz-jruby examples/.../deseq2_airway_galaaz.rb (repo root).
+# Run: bin/galaaz-ruby examples/.../deseq2_airway_galaaz.rb (repo root).
 
 require 'galaaz'
 
@@ -2728,8 +2752,8 @@ arguments.
 
 * Fork it
 * Create your feature branch (`git checkout -b my-new-feature`)
-* Write tests — use **`bin/run_rspec`** or **`bin/run_all_rspec`** with **JRuby** so JVM flags and
-  the load path match **`docs/testing.md`**
+* Write tests — use **`bin/run_rspec`** or **`bin/run_all_rspec`** (JRuby or CRuby via
+  **`GALAAZ_RUBY`**) so the load path matches **`docs/testing.md`**
 * Commit your changes (`git commit -am 'Add some feature'`)
 * Push to the branch (`git push origin my-new-feature`)
 * Open a pull request

data/blogs/manual/manual.md

@@ -2,7 +2,7 @@
 title: "Galaaz Manual"
 subtitle: "R-on-Rails: GNU R meets Ruby for the web"
 author: "Rodrigo Botafogo"
-tags: [Galaaz, "R-on-Rails", Ruby, Rails, JRuby, R, "GNU R", ggplot2, knitr, dplyr, Bioconductor, Arrow]
+tags: [Galaaz, "R-on-Rails", Ruby, Rails, JRuby, CRuby, R, "GNU R", ggplot2, knitr, dplyr, Bioconductor, Arrow]
 date: "2026"
 bibliography: "../../examples/Bibliography/stats.bib"
 output:
@@ -358,7 +358,13 @@ A **table of all `bin/` scripts** (bootstrap, Ruby launcher, gstudio, gknit, tes
    **`bin/run_all_rspec`** (same `GALAAZ_RUBY` rule). **`bin/galaaz-jruby`** remains a thin
    wrapper that forces JRuby.
 
-A **gstudio** try image (JRuby + R + Galaaz already installed) is **`docker run --rm -it ghcr.io/rbotafogo/galaaz-try:gstudio`** (or **`./docker/try-gstudio/run.sh`** from a checkout). Maintainers can prove a RubyGems install on a throwaway Ubuntu machine (no repo inside the container) with **`./docker/cold-install/run.sh published-specs`** (JRuby) or **`./docker/cold-install-cruby/run.sh published-specs`** (CRuby).
+A **gstudio** try image with Galaaz already installed is available for both engines:
+**JRuby** — `docker run --rm -it ghcr.io/rbotafogo/galaaz-try:gstudio` (or
+`./docker/try-gstudio/run.sh` from a checkout); **CRuby** —
+`docker run --rm -it ghcr.io/rbotafogo/galaaz-try:cruby` (or `./docker/try-cruby/run.sh`).
+Maintainers can prove a RubyGems install on a throwaway Ubuntu machine (no repo inside
+the container) with `./docker/cold-install/run.sh published-specs` (JRuby) or
+`./docker/cold-install-cruby/run.sh published-specs` (CRuby).
 
 ## Windows + WSL2 (optional: Docker / R in a container)
 
@@ -394,11 +400,18 @@ WSL integration is enabled for the distro where Galaaz is installed.
 ``` ruby
   vec = R.c(1, 2, 3, 4)
   puts vec
+
+  # R.foo(...) calls an R *function*. Datasets are objects — fetch with ~:
+  df = ~R[:mtcars]
+  puts R.summary(df)
 ```
 
 ```
 ## [1] 1 2 3 4
 ```
+
+(`R.mtcars` is wrong: it becomes `mtcars()` in R and fails. With
+`using Galaaz::SymbolDSL`, the short form `~:mtcars` also works.)
   
 * Run all specs
 
@@ -4261,10 +4274,11 @@ pulls in several dependencies; the first install can take several minutes.
 ## Example: DESeq2 on the airway dataset
 
 The script **`examples/bioconductor_deseq2_airway/deseq2_airway_galaaz.rb`** is the canonical
-version in the repository. Run it from the **Galaaz repository root** with JRuby, for example:
+version in the repository. Run it from the **Galaaz repository root** with either engine, for example:
 
 ```text
-bin/galaaz-jruby examples/bioconductor_deseq2_airway/deseq2_airway_galaaz.rb
+bin/galaaz-ruby examples/bioconductor_deseq2_airway/deseq2_airway_galaaz.rb
+# or: bin/galaaz-jruby examples/bioconductor_deseq2_airway/deseq2_airway_galaaz.rb
 ```
 
 The workflow in Ruby mirrors a standard DESeq2 vignette:
@@ -4293,7 +4307,7 @@ manual is knitted, because **DESeq2** is heavy and may be absent on the build ma
 
 ``` ruby
 # Canonical script: examples/bioconductor_deseq2_airway/deseq2_airway_galaaz.rb
-# Run: bin/galaaz-jruby examples/.../deseq2_airway_galaaz.rb (repo root).
+# Run: bin/galaaz-ruby examples/.../deseq2_airway_galaaz.rb (repo root).
 
 require 'galaaz'
 

data/blogs/oh_my/oh_my.Rmd

@@ -3,7 +3,7 @@ title: "Extending R with classes, modules, procs, lambdas, oh my!"
 author:
     - "Rodrigo Botafogo"
     - "Daniel Mossé - University of Pittsburgh"
-tags: [Tech, Data Science, Ruby, R, JRuby, "GNU R", Galaaz]
+tags: [Tech, Data Science, Ruby, R, JRuby, CRuby, "GNU R", Galaaz]
 date: "November 19th, 2018 (narrative updated for Galaaz 2.0, 2026)"
 output:
   html_document:
@@ -34,10 +34,10 @@ or similar solutions in Python,
 such as [PypeR](https://pypi.python.org/pypi/PypeR/1.1.0), [rpy2](http://rpy2.bitbucket.org/)
 and other similar solutions.
 
-**Galaaz 2.0** runs on **[JRuby](https://www.jruby.org/)** and drives **GNU R** through a **bridge**,
-so Ruby code can create and manipulate R objects and call R functions while staying idiomatic Ruby.
-An earlier prototype used Oracle’s **GraalVM** with **TruffleRuby** and **FastR**; that stack is
-historical and is **not** what current Galaaz targets.
+**Galaaz 2.0** supports **[JRuby](https://www.jruby.org/)** or **CRuby** equally and drives
+**GNU R** through a **bridge**, so Ruby code can create and manipulate R objects and call R
+functions while staying idiomatic Ruby. An earlier prototype used Oracle’s **GraalVM** with
+**TruffleRuby** and **FastR**; that stack is historical and is **not** what current Galaaz targets.
 
 
 # Bases of Object Programming
@@ -1673,7 +1673,7 @@ For those interested in Ruby and science, we recommend:
 
 * http://sciruby.com/
 
-**Galaaz 2.0** runs on **JRuby** and talks to **GNU R** through the bridge described in this
+**Galaaz 2.0** runs on **JRuby or CRuby** and talks to **GNU R** through the bridge described in this
 series — the same integration model used throughout the examples above.
 
 # Callbacks and R calling into Ruby
@@ -1695,7 +1695,7 @@ path in Galaaz 2.0.
 
 # Conclusions II
 
-**JRuby + GNU R + Galaaz** gives a practical polyglot stack: idiomatic Ruby for structure and
+**JRuby or CRuby + GNU R + Galaaz** gives a practical polyglot stack: idiomatic Ruby for structure and
 libraries, GNU R for statistics and the CRAN/Bioconductor ecosystem, and Galaaz as the bridge
 between them.  As always, choose the right tools for the job at hand — and when the job sits
 between an R-only workflow and a broader polyglot application, Galaaz is designed to connect those

data/blogs/oh_my/oh_my.md

@@ -3,7 +3,7 @@ title: "Extending R with classes, modules, procs, lambdas, oh my!"
 author:
     - "Rodrigo Botafogo"
     - "Daniel Mossé - University of Pittsburgh"
-tags: [Tech, Data Science, Ruby, R, JRuby, "GNU R", Galaaz]
+tags: [Tech, Data Science, Ruby, R, JRuby, CRuby, "GNU R", Galaaz]
 date: "November 19th, 2018 (narrative updated for Galaaz 2.0, 2026)"
 output:
   html_document:
@@ -32,10 +32,10 @@ or similar solutions in Python,
 such as [PypeR](https://pypi.python.org/pypi/PypeR/1.1.0), [rpy2](http://rpy2.bitbucket.org/)
 and other similar solutions.
 
-**Galaaz 2.0** runs on **[JRuby](https://www.jruby.org/)** and drives **GNU R** through a **bridge**,
-so Ruby code can create and manipulate R objects and call R functions while staying idiomatic Ruby.
-An earlier prototype used Oracle’s **GraalVM** with **TruffleRuby** and **FastR**; that stack is
-historical and is **not** what current Galaaz targets.
+**Galaaz 2.0** supports **[JRuby](https://www.jruby.org/)** or **CRuby** equally and drives
+**GNU R** through a **bridge**, so Ruby code can create and manipulate R objects and call R
+functions while staying idiomatic Ruby. An earlier prototype used Oracle’s **GraalVM** with
+**TruffleRuby** and **FastR**; that stack is historical and is **not** what current Galaaz targets.
 
 
 # Bases of Object Programming
@@ -2148,7 +2148,7 @@ For those interested in Ruby and science, we recommend:
 
 * http://sciruby.com/
 
-**Galaaz 2.0** runs on **JRuby** and talks to **GNU R** through the bridge described in this
+**Galaaz 2.0** runs on **JRuby or CRuby** and talks to **GNU R** through the bridge described in this
 series — the same integration model used throughout the examples above.
 
 # Callbacks and R calling into Ruby
@@ -2170,7 +2170,7 @@ path in Galaaz 2.0.
 
 # Conclusions II
 
-**JRuby + GNU R + Galaaz** gives a practical polyglot stack: idiomatic Ruby for structure and
+**JRuby or CRuby + GNU R + Galaaz** gives a practical polyglot stack: idiomatic Ruby for structure and
 libraries, GNU R for statistics and the CRAN/Bioconductor ecosystem, and Galaaz as the bridge
 between them.  As always, choose the right tools for the job at hand — and when the job sits
 between an R-only workflow and a broader polyglot application, Galaaz is designed to connect those

data/blogs/ruby_plot/ruby_plot.Rmd

@@ -3,7 +3,7 @@ title: "How to make Beautiful Ruby Plots with Galaaz"
 author:
     - "Rodrigo Botafogo"
     - "Daniel Mossé - University of Pittsburgh"
-tags: [Tech, Data Science, Ruby, R, JRuby, "GNU R", Galaaz]
+tags: [Tech, Data Science, Ruby, R, JRuby, CRuby, "GNU R", Galaaz]
 date: "November 19th, 2018 (narrative updated for Galaaz 2.0, 2026)"
 output:
   html_document:
@@ -46,16 +46,16 @@ of libraries for data analysis.
 Until recently, there was no real perspective for Ruby to bridge this gap.
 Implementing a complete scientific computing infrastructure would take too long.
 
-**Galaaz 2.0** couples **[JRuby](https://www.jruby.org/)** (Ruby on the JVM) with **GNU R**—the
-same R distribution used for data science everywhere. A **bridge** evaluates R from Ruby and
-exchanges data between the two processes so that, from Ruby, you call R functions and work
+**Galaaz 2.0** supports **[JRuby](https://www.jruby.org/)** or **CRuby** equally and drives
+**GNU R**—the same R distribution used for data science everywhere. A **bridge** evaluates R from
+Ruby and exchanges data between the two processes so that, from Ruby, you call R functions and work
 with R objects using familiar Ruby syntax. In other words, a Ruby programmer can use the
 capabilities of R without memorizing all of R’s syntax for day-to-day tasks.
 
 An **earlier line of work** used Oracle’s **GraalVM** with **TruffleRuby** and **FastR** so that
 Ruby and R could share one JVM runtime. That stack is **no longer** what Galaaz targets;
-today’s Galaaz is developed and tested with **JRuby + GNU R** (see the project manual for setup
-and command-line tools).
+today’s Galaaz is developed and tested with **JRuby or CRuby + GNU R** (see the project manual for
+setup and command-line tools).
 
 Library wrapping is a common way to bring features from one language into another.
 To improve performance, Python often wraps more efficient C libraries. For the
@@ -84,7 +84,7 @@ ggplot themes that will work the same as the Ruby module.  Yet, writing a new th
 requires specific knowledge on theme writing.  Ruby modules are standard to the
 language and don't need special knowledge.
 
-[Here](https://towardsdatascience.com/ruby-plotting-with-galaaz-an-example-of-tightly-coupling-ruby-and-r-in-graalvm-520b69e21021) is an older article (GraalVM-era Galaaz) with a scatter plot in Ruby; the **ideas** still apply under Galaaz 2.0 with JRuby and GNU R.
+[Here](https://towardsdatascience.com/ruby-plotting-with-galaaz-an-example-of-tightly-coupling-ruby-and-r-in-graalvm-520b69e21021) is an older article (GraalVM-era Galaaz) with a scatter plot in Ruby; the **ideas** still apply under Galaaz 2.0 with JRuby or CRuby and GNU R.
 
 # gKnit
 
@@ -549,12 +549,12 @@ Trying to bring to Ruby the power of R starting from scratch is an enormous ende
 and would probably never be accomplished.  Today's data scientists would certainly
 stick with either Python or R.  Now, both the Ruby and R communities can benefit
 from this marriage: **Galaaz 2.0** uses **standard GNU R** for statistics and graphics
-and **JRuby** for application code, threading, and the JVM ecosystem.  We presented
-the process to couple Ruby and R; the coupling is implemented by the Galaaz bridge and
-**gKnit** for literate documents, not by a single GraalVM polyglot runtime.
+and **JRuby or CRuby** for application code (prefer **JRuby** when you want real threads and the
+JVM ecosystem).  We presented the process to couple Ruby and R; the coupling is implemented by the
+Galaaz bridge and **gKnit** for literate documents, not by a single GraalVM polyglot runtime.
 
 For performance, expect **ordinary GNU R** behaviour for model fitting and plotting, while
-**JRuby** gives **real parallel threads** on the Ruby side and access to Java libraries when
+**JRuby** can give **real parallel threads** on the Ruby side and access to Java libraries when
 you need them.
 
 This article has shown how to improve a plot step-by-step.  Starting from a very simple
@@ -571,8 +571,7 @@ be of great help for any Rubyist trying to write articles, blogs or documentatio
 
 ## Prerequisites (Galaaz 2.0)
 
-* **JRuby** — Ruby on the JVM ([jruby.org](https://www.jruby.org/))
-* A **JDK** compatible with your JRuby version
+* **JRuby** and a compatible **JDK**, *or* **CRuby 3.3+**
 * **GNU R** — `R` on your `PATH`, with compilers/tools available if packages must be built from source
 
 The following R packages will be automatically installed when necessary, but could be installed prior
@@ -594,4 +593,4 @@ are commonly required.
 
 * From the Galaaz repository (or your installed layout), render documents with **`bin/gknit`** (see the project manual for flags such as `--output_format all`).
 * In Ruby code: `require 'galaaz'`
-* For running scripts with the correct JRuby and JVM options, use **`bin/galaaz-jruby`** as described in the manual.
+* Run Ruby with **`bin/galaaz-ruby`** (either engine) or **`bin/galaaz-jruby`** when you need JRuby JVM flags (see the manual).

data/blogs/ruby_plot/ruby_plot.md

@@ -3,7 +3,7 @@ title: "How to make Beautiful Ruby Plots with Galaaz"
 author:
     - "Rodrigo Botafogo"
     - "Daniel Mossé - University of Pittsburgh"
-tags: [Tech, Data Science, Ruby, R, JRuby, "GNU R", Galaaz]
+tags: [Tech, Data Science, Ruby, R, JRuby, CRuby, "GNU R", Galaaz]
 date: "November 19th, 2018 (narrative updated for Galaaz 2.0, 2026)"
 output:
   html_document:
@@ -42,16 +42,16 @@ of libraries for data analysis.
 Until recently, there was no real perspective for Ruby to bridge this gap.
 Implementing a complete scientific computing infrastructure would take too long.
 
-**Galaaz 2.0** couples **[JRuby](https://www.jruby.org/)** (Ruby on the JVM) with **GNU R**—the
-same R distribution used for data science everywhere. A **bridge** evaluates R from Ruby and
-exchanges data between the two processes so that, from Ruby, you call R functions and work
+**Galaaz 2.0** supports **[JRuby](https://www.jruby.org/)** or **CRuby** equally and drives
+**GNU R**—the same R distribution used for data science everywhere. A **bridge** evaluates R from
+Ruby and exchanges data between the two processes so that, from Ruby, you call R functions and work
 with R objects using familiar Ruby syntax. In other words, a Ruby programmer can use the
 capabilities of R without memorizing all of R’s syntax for day-to-day tasks.
 
 An **earlier line of work** used Oracle’s **GraalVM** with **TruffleRuby** and **FastR** so that
 Ruby and R could share one JVM runtime. That stack is **no longer** what Galaaz targets;
-today’s Galaaz is developed and tested with **JRuby + GNU R** (see the project manual for setup
-and command-line tools).
+today’s Galaaz is developed and tested with **JRuby or CRuby + GNU R** (see the project manual for
+setup and command-line tools).
 
 Library wrapping is a usual way of bringing features from one language into another.
 To improve performance, Python often wraps more efficient C libraries. For the
@@ -80,7 +80,7 @@ ggplot themes that will work the same as the Ruby module.  Yet, writing a new th
 requires specific knowledge on theme writing.  Ruby modules are standard to the
 language and don't need special knowledge.
 
-[Here](https://towardsdatascience.com/ruby-plotting-with-galaaz-an-example-of-tightly-coupling-ruby-and-r-in-graalvm-520b69e21021) is an older article (GraalVM-era Galaaz) with a scatter plot in Ruby; the **ideas** still apply under Galaaz 2.0 with JRuby and GNU R.
+[Here](https://towardsdatascience.com/ruby-plotting-with-galaaz-an-example-of-tightly-coupling-ruby-and-r-in-graalvm-520b69e21021) is an older article (GraalVM-era Galaaz) with a scatter plot in Ruby; the **ideas** still apply under Galaaz 2.0 with JRuby or CRuby and GNU R.
 
 # gKnit
 
@@ -622,12 +622,12 @@ Trying to bring to Ruby the power of R starting from scratch is an enormous ende
 and would probably never be accomplished.  Today's data scientists would certainly
 stick with either Python or R.  Now, both the Ruby and R communities can benefit
 from this marriage: **Galaaz 2.0** uses **standard GNU R** for statistics and graphics
-and **JRuby** for application code, threading, and the JVM ecosystem.  We presented
-the process to couple Ruby and R; the coupling is implemented by the Galaaz bridge and
-**gKnit** for literate documents, not by a single GraalVM polyglot runtime.
+and **JRuby or CRuby** for application code (prefer **JRuby** when you want real threads and the
+JVM ecosystem).  We presented the process to couple Ruby and R; the coupling is implemented by the
+Galaaz bridge and **gKnit** for literate documents, not by a single GraalVM polyglot runtime.
 
 For performance, expect **ordinary GNU R** behaviour for model fitting and plotting, while
-**JRuby** gives **real parallel threads** on the Ruby side and access to Java libraries when
+**JRuby** can give **real parallel threads** on the Ruby side and access to Java libraries when
 you need them.
 
 This article has shown how to improve a plot step-by-step.  Starting from a very simple
@@ -644,8 +644,7 @@ be of great help for any Rubyist trying to write articles, blogs or documentatio
 
 ## Prerequisites (Galaaz 2.0)
 
-* **JRuby** — Ruby on the JVM ([jruby.org](https://www.jruby.org/))
-* A **JDK** compatible with your JRuby version
+* **JRuby** and a compatible **JDK**, *or* **CRuby 3.3+**
 * **GNU R** — `R` on your `PATH`, with compilers/tools available if packages must be built from source
 
 The following R packages will be automatically installed when necessary, but could be installed prior
@@ -667,4 +666,4 @@ are commonly required.
 
 * From the Galaaz repository (or your installed layout), render documents with **`bin/gknit`** (see the project manual for flags such as `--output_format all`).
 * In Ruby code: `require 'galaaz'`
-* For running scripts with the correct JRuby and JVM options, use **`bin/galaaz-jruby`** as described in the manual.
+* Run Ruby with **`bin/galaaz-ruby`** (either engine) or **`bin/galaaz-jruby`** when you need JRuby JVM flags (see the manual).

data/examples/misc/ggplot.rb

@@ -151,7 +151,7 @@ R.grid__newpage
 # R.dev__off('')
 # R.awt
 
-(R.ggplot(R.mtcars, E.aes(x: :wt, y: :mpg)) +
+(R.ggplot(~:mtcars, E.aes(x: :wt, y: :mpg)) +
  R.geom_point('')).print
 =end
 

data/lib/galaaz/cli.rb

@@ -315,6 +315,12 @@ module Galaaz
     end
 
     def add_arrow
+      # R 'arrow' needs a matching libarrow. Compiling Arrow C++ + Boost from the
+      # CRAN source tarball is fragile (especially Arch/Omarchy). Distro libarrow
+      # (e.g. Arch extra/arrow) often mismatches the CRAN package major and then
+      # pkg-config configure fails. Apache's version-matched prebuilt libarrow is
+      # the reliable automated path — HTTPS from Apache, no interactive steps.
+      prepare_arrow_cran_env!
       pkgs = read_pkg_list('arrow.txt')
       install_cran!(pkgs)
       if RUBY_ENGINE == 'ruby'
@@ -330,6 +336,17 @@ module Galaaz
       0
     end
 
+    # Env for install.packages("arrow") — see https://arrow.apache.org/docs/r/articles/install.html
+    def prepare_arrow_cran_env!
+      ENV['LIBARROW_BINARY'] = 'true'
+      ENV['NOT_CRAN'] = 'true'
+      # Do not fall back to the Boost/C++ source build that breaks on Arch.
+      ENV['LIBARROW_BUILD'] = 'false'
+      # Avoid linking against a mismatched system libarrow (e.g. pacman 24.x vs CRAN 25.x).
+      ENV['ARROW_USE_PKG_CONFIG'] = 'false'
+      puts 'galaaz add arrow: LIBARROW_BINARY=true (Apache prebuilt libarrow; no source build)'
+    end
+
     def add_tex
       unless command_present?('pandoc')
         warn 'galaaz add tex: pandoc not on PATH — install via your package manager (e.g. pacman -S pandoc)'
@@ -400,20 +417,21 @@ module Galaaz
         abort_unless(ok, 'git clone failed (is the ledger repo public/reachable?)')
       end
 
-      gemfile = File.join(dest, 'Gemfile')
-      text = File.read(gemfile)
-      rewritten = text.gsub(/gem\s+["']galaaz["']\s*,\s*path:\s*["'][^"']+["']/, 'gem "galaaz"')
-      if rewritten != text
-        File.write(gemfile, rewritten)
-        puts 'galaaz add ledger: Gemfile now uses RubyGems galaaz (no path:)'
-      end
+      ensure_ledger_galaaz_gemfile!(File.join(dest, 'Gemfile'))
 
       Dir.chdir(dest) do
         need_cmd!('bundle')
-        abort_unless(system('bundle', 'install'), 'bundle install failed')
-        # Ensure gatekeeper for the bundled/installed gem path when possible.
-        system('galaaz', 'setup') || warn('galaaz add ledger: galaaz setup returned non-zero; check gatekeeper')
+        # Lockfile often still pins path: ../galaaz @ an old version — pull latest RubyGems.
+        puts 'galaaz add ledger: bundle update galaaz'
+        unless system('bundle', 'update', 'galaaz')
+          abort_unless(system('bundle', 'install'), 'bundle install failed')
+        end
+        # Setup the gem Bundler will load (not PATH galaaz, which may differ).
+        puts 'galaaz add ledger: bundle exec galaaz setup'
+        system('bundle', 'exec', 'galaaz', 'setup') ||
+          warn('galaaz add ledger: bundle exec galaaz setup returned non-zero; check gatekeeper')
         abort_unless(system('bin/rails', 'db:prepare'), 'rails db:prepare failed')
+        abort_unless(system('bin/rails', 'db:migrate'), 'rails db:migrate failed')
         abort_unless(system({ 'SEED_PROFILE' => 'fast' }, 'bin/rails', 'db:seed'), 'rails db:seed failed')
       end
 
@@ -424,6 +442,21 @@ module Galaaz
       0
     end
 
+    # Ledger repo may ship `gem "galaaz", path: "..."`. Standalone installs use RubyGems
+    # (CRuby or JRuby), unpinned, so `bundle update galaaz` takes the newest published gem.
+    def ensure_ledger_galaaz_gemfile!(gemfile)
+      text = File.read(gemfile)
+      line = 'gem "galaaz"'
+      rewritten = text.gsub(/^\s*gem\s+["']galaaz["'].*$/, line)
+      if rewritten == text && text !~ /^\s*gem\s+["']galaaz["']/
+        rewritten = text + "\n#{line}\n"
+      end
+      if rewritten != text
+        File.write(gemfile, rewritten)
+        puts 'galaaz add ledger: Gemfile → gem "galaaz" (RubyGems latest; not path:)'
+      end
+    end
+
     # ---- helpers ----
 
     class CliError < StandardError; end

data/version.rb

@@ -1,2 +1,2 @@
 $gem_name = "galaaz"
-$version="2.1.4"
+$version="2.1.5"

metadata

@@ -1,14 +1,13 @@
 --- !ruby/object:Gem::Specification
 name: galaaz
 version: !ruby/object:Gem::Version
-  version: 2.1.4
+  version: 2.1.5
 platform: ruby
 authors:
 - Rodrigo Botafogo
-autorequire:
 bindir: bin
 cert_chain: []
-date: 2026-09-04 00:00:00.000000000 Z
+date: 2026-09-07 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: msgpack
@@ -87,11 +86,11 @@ description: |
 email: rodrigo.a.botafogo@gmail.com
 executables:
 - galaaz
-- gstudio
-- gknit
 - gbookdown
-- grun
+- gknit
 - gknit-draft
+- grun
+- gstudio
 extensions: []
 extra_rdoc_files: []
 files:
@@ -487,7 +486,6 @@ metadata:
   documentation_uri: https://rbotafogo.github.io/galaaz/
   changelog_uri: https://github.com/rbotafogo/galaaz/blob/galaaz2_0/CHANGELOG.md
   yard.run: yri
-post_install_message:
 rdoc_options: []
 require_paths:
 - lib
@@ -502,8 +500,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
     - !ruby/object:Gem::Version
       version: '0'
 requirements: []
-rubygems_version: 3.5.22
-signing_key:
+rubygems_version: 4.0.3
 specification_version: 4
 summary: 'R-on-Rails: tightly couple Ruby and GNU R for data science on the web'
 test_files: []