← Back to home
Comparison · Infra & APIs

retroharmonize vs Rhino

A side-by-side editorial comparison of retroharmonize and Rhino — release velocity, themes, recent moves, and the top alternatives to consider.

retroharmonize vs Rhino: at a glance

FeatureretroharmonizeRhino
SectorInfra & APIsInfra & APIs
Velocity score0.00.0
Sparks · 30d00
Top themessurvey-data, data-harmonization, labelled-data, reproducibilityr-shiny, scaffolding, agent-instructions, release-candidates
Last editorial update54m ago5d ago
WebsiteVisit →Visit →

What is retroharmonize?

Survey harmonization tooling that spent its last release earning its way back onto CRAN.

retroharmonize handles retrospective harmonization of survey microdata — reconciling value codes, value labels, variable names, and missing-value ranges across waves so separate surveys can be joined or panelled reproducibly. The most recent release was not about any of that: the package had been archived from CRAN when a dependency was archived, and the work went into refactoring the labelled_spss_survey vctrs integration, separating core, print, arithmetic, and vctrs methods, and passing checks across five platforms plus R-devel.

Read the full retroharmonize trajectory →

What is Rhino?

Rhino's release line runs on release candidates, and 1.12 makes room for coding agents.

Rhino publishes only release candidates to this feed — every entry back to 1.9 is an -rc tag, with no final release ever appearing. The 1.12.0 candidate is the first in the window with user-visible substance: a `use` function that scaffolds an AGENTS.md file carrying Rhino-specific instructions, plus a `use` function for the CI template. The rest is maintenance: covr-based test coverage, e2e tests, Node dependency updates, and a maintainer handover.

Read the full Rhino trajectory →

retroharmonize vs Rhino: editorial side-by-side

R
retroharmonize
INFRA · APIS
0.0

Survey harmonization tooling that spent its last release earning its way back onto CRAN.

◆ Current state

retroharmonize handles retrospective harmonization of survey microdata — reconciling value codes, value labels, variable names, and missing-value ranges across waves so separate surveys can be joined or panelled reproducibly. The most recent release was not about any of that: the package had been archived from CRAN when a dependency was archived, and the work went into refactoring the labelled_spss_survey vctrs integration, separating core, print, arithmetic, and vctrs methods, and passing checks across five platforms plus R-devel.

◆ Where it's heading

The design bet has been constant since the first release — comprehensive S3 classes that carry labels and missing-value semantics through every transformation, so the harmonization is documented rather than reconstructed. What has changed is where effort goes. Early releases added harmonization functions and a worked Arab Barometer case study; recent ones are code quality and CRAN survival. Note that the version numbering in this feed is not monotonic: 0.1.13 was released roughly nine months before 0.1.7, so version order here does not indicate release order.

◆ Prediction

Having just restored CRAN availability through a refactor rather than a feature, the near-term work is most likely consolidation of the vctrs integration the notes describe rather than new harmonization functions.

R
Rhino
INFRA · APIS
0.0

Rhino's release line runs on release candidates, and 1.12 makes room for coding agents.

◆ Current state

Rhino publishes only release candidates to this feed — every entry back to 1.9 is an -rc tag, with no final release ever appearing. The 1.12.0 candidate is the first in the window with user-visible substance: a `use` function that scaffolds an AGENTS.md file carrying Rhino-specific instructions, plus a `use` function for the CI template. The rest is maintenance: covr-based test coverage, e2e tests, Node dependency updates, and a maintainer handover.

◆ Where it's heading

Rhino is converging on scaffolding as its main surface — the framework's value is increasingly in what it generates for you rather than what it does at runtime, and 1.12 extends that generation to instructions meant for AI coding agents rather than humans. The maintainer change and the CI/coverage work in the same release read as consolidation after a long gap: 1.11 shipped in April 2025, 1.12 not until June 2026.

◆ Prediction

More `use_*` scaffolding functions are the obvious next increment, since two arrived in a single release. Whether the AGENTS.md instructions grow into deeper agent tooling is not something these entries settle.

Alternatives to retroharmonize and Rhino

Other Infra & APIs products tracked by Sparkpulse, ranked by recent ship velocity. Each card links to a full editorial trajectory and lets you pivot into a head-to-head comparison with either retroharmonize or Rhino.

See all retroharmonize alternatives → · See all Rhino alternatives →

Recent activity from retroharmonize and Rhino

Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.

  1. 2mo agoRhinoRhino 1.12 adds AGENTS.md and CI-template scaffolding
  2. 3mo agoretroharmonizeCRAN modernisation release
  3. 7mo agoretroharmonizeRelease candidate; notes cite code quality with no detail
  4. 1y agoRhinoRhino 1.11.0 release candidate
  5. 1y agoRhinoRhino 1.10.0 release candidate
  6. 2y agoRhinoRhino 1.9 adds bslib support and prettier formatting
  7. 4y agoretroharmonizeImproved documentation
  8. 5y agoretroharmonize0.1.7 With case study on harmonizing Arab Barometer surveys
  9. 5y agoretroharmonizeretroharmonize 0.1.13 is on CRAN
  10. 6y agoretroharmonize0.1.0 Retrospective harmonization of survey data files in R

Frequently asked questions

What is the difference between retroharmonize and Rhino?

They serve adjacent needs but don't currently overlap on shipped themes. retroharmonize and Rhino are shipping at a similar cadence (velocity 0.0 vs 0.0, both within Sparkpulse's "active" band). See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.

Is retroharmonize better than Rhino?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. retroharmonize and Rhino are shipping at a similar cadence (velocity 0.0 vs 0.0, both within Sparkpulse's "active" band). For your specific use case, the alternatives sections above list other Infra & APIs products to evaluate alongside.

What are the best alternatives to retroharmonize?

Top retroharmonize alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "retroharmonize alternatives" section above for the current picks, or visit /alternatives/retroharmonize for the full list with editorial commentary on each.

What are the best alternatives to Rhino?

Top Rhino alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Rhino alternatives" section above for the current picks, or visit /alternatives/rhino-r for the full list with editorial commentary on each.