WPML
WPML made machine translation the default, and its point releases keep chasing WordPress and page builders.
A side-by-side editorial comparison of KRLS and Rhino — release velocity, themes, recent moves, and the top alternatives to consider.
A 2014 kernel regression method getting the scalability and tooling it never had, in a three-release afternoon.
KRLS fits kernel regularized least squares, a method whose exact form requires an n-by-n kernel matrix and therefore stops being usable well before modern sample sizes. Three releases shipped within 33 minutes of each other addressed exactly that: a Nystrom approximation mode with conditional approximate inference, kmeans landmark selection with an accessor for reusing landmarks across fits, and GCV as an alternative to leave-one-out for choosing lambda. The default path remains the exact one, and existing calls are unchanged.
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.
KRLS fits kernel regularized least squares, a method whose exact form requires an n-by-n kernel matrix and therefore stops being usable well before modern sample sizes. Three releases shipped within 33 minutes of each other addressed exactly that: a Nystrom approximation mode with conditional approximate inference, kmeans landmark selection with an accessor for reusing landmarks across fits, and GCV as an alternative to leave-one-out for choosing lambda. The default path remains the exact one, and existing calls are unchanged.
The package is being modernized on two tracks that reinforce each other. The interface track — a formula method, broom extractors, autoplot, summary and glance diagnostics — makes the estimator fit contemporary R workflows without touching the algorithm, and the notes are explicit that existing matrix-interface calls remain bit-identical. The performance track removes the reasons it could not be run at all: the Nystrom mode for the kernel matrix, and an average-marginal-effects variance computation rewritten via a row-sum identity to quadratic per-predictor cost. Everything is added as opt-in, which suggests the goal is reaching new users without disturbing replication of published results.
With approximation, landmark reuse, and a second lambda criterion now in place, the remaining gap is guidance on when to trust them; the scaling vignette shipped alongside GCV points to more empirical validation rather than new estimation machinery.
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.
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.
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.
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 KRLS or Rhino.
WPML made machine translation the default, and its point releases keep chasing WordPress and page builders.
A forest plot package that keeps handing users control of one more graphical detail.
Interval-valued data plotting, spending 2026 making its function names and examples survive CRAN.
A microbiome network model that got itself un-archived by deleting the dependency that killed it.
Three releases in ten days, every one of them a CRAN reviewer's correction rather than a code change.
Pipeline provenance for tidyverse workflows, recording what changed at each step without keeping the data.
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. KRLS 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.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. KRLS 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.
Top KRLS alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "KRLS alternatives" section above for the current picks, or visit /alternatives/krls for the full list with editorial commentary on each.
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.