← Back to home
Comparison · Infra & APIs

Rhino vs waldo

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

Shared themes:maintenance

Rhino vs waldo: at a glance

FeatureRhinowaldo
SectorInfra & APIsInfra & APIs
Velocity score0.00.0
Sparks · 30d00
Top themesr-shiny, scaffolding, agent-instructions, release-candidatestesting, diffing, dependencies, s7
Last editorial update1h ago6h ago
WebsiteVisit →Visit →

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 →

What is waldo?

waldo keeps shedding dependencies while teaching its diff engine new object systems

waldo produces the object comparisons that testthat failure messages are built from. The recent releases do two things: drop dependencies - tibble, rematch2 and fansi have all gone - and extend comparison to object systems that did not exist when it was written, notably S7. Correctness of missing-value and tolerance semantics accounts for most of the rest.

Read the full waldo trajectory →

Rhino vs waldo: editorial side-by-side

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.

W
waldo
INFRA · APIS
0.0

waldo keeps shedding dependencies while teaching its diff engine new object systems

◆ Current state

waldo produces the object comparisons that testthat failure messages are built from. The recent releases do two things: drop dependencies - tibble, rematch2 and fansi have all gone - and extend comparison to object systems that did not exist when it was written, notably S7. Correctness of missing-value and tolerance semantics accounts for most of the rest.

◆ Where it's heading

This is a package deliberately shrinking its footprint while widening what it understands. Since it is imported by testthat, every dependency it drops is one fewer package in the check environment of most of CRAN, which is clearly the motivation. The comparison logic itself changes only when R gains a new way to represent objects.

◆ Prediction

Expect S7 support to deepen from basic to complete as S7 adoption grows, and further dependency removals; the diff algorithm itself looks settled.

Alternatives to Rhino and waldo

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 Rhino or waldo.

See all Rhino alternatives → · See all waldo alternatives →

Recent activity from Rhino and waldo

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

  1. 2mo agoRhinoRhino 1.12 adds AGENTS.md and CI-template scaffolding
  2. 1y agowaldoCompares weakrefs, ignores read-only S7 properties
  3. 1y agoRhinoRhino 1.11.0 release candidate
  4. 1y agowaldoOnly uses bit64 comparison when bit64 is installed
  5. 1y agowaldoDrops tibble and rematch2; adds basic S7 support
  6. 1y agoRhinoRhino 1.10.0 release candidate
  7. 1y agowaldoDrops the fansi dependency
  8. 2y agoRhinoRhino 1.9 adds bslib support and prettier formatting
  9. 2y agowaldoFixes for upcoming R-devel changes
  10. 3y agowaldoTolerance now governs both display and NaN equality

Frequently asked questions

What is the difference between Rhino and waldo?

Both compete on the same themes — maintenance — within Infra & APIs. Rhino and waldo 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 Rhino better than waldo?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Rhino and waldo 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 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.

What are the best alternatives to waldo?

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