r2rtf
The clinical-report table engine learned Chinese, then learned to leave RTF entirely
A side-by-side editorial comparison of orbital and slider — release velocity, themes, recent moves, and the top alternatives to consider.
Turning fitted tidymodels into SQL, one model family at a time — and the boosting engines just landed.
orbital converts a fitted tidymodels workflow into a database expression so prediction runs where the data lives, no R session in the loop. Its value is entirely a function of coverage, and 0.5.0 was the largest coverage release yet: catboost and lightgbm boosted trees, rpart decision trees, earth-backed MARS, glmnet multinomial regression, and both randomForest and ranger random forests, all for numeric, class, and probability predictions. The 0.5.1 follow-up is corrective, fixing SQL that Snowflake and other engines rejected because it cast booleans directly to numeric.
Feature-complete since 2021, and every release since has been paying CRAN's C API bill
slider provides sliding-window and index-aware window functions for R, with a C implementation underneath and a specialised fast path for common aggregations. The user-facing surface has been stable since 0.3.0 in late 2022. Everything after that is compliance and platform work: STRING_PTR removed in 0.3.2, OBJECT() removed in 0.3.3, a vctrs callable's C signature corrected, and the minimum R version raised twice.
orbital converts a fitted tidymodels workflow into a database expression so prediction runs where the data lives, no R session in the loop. Its value is entirely a function of coverage, and 0.5.0 was the largest coverage release yet: catboost and lightgbm boosted trees, rpart decision trees, earth-backed MARS, glmnet multinomial regression, and both randomForest and ranger random forests, all for numeric, class, and probability predictions. The 0.5.1 follow-up is corrective, fixing SQL that Snowflake and other engines rejected because it cast booleans directly to numeric.
The package has been working outward in rings: recipe preprocessing steps first, then model types, then post-processing via the tailor package in 0.4.0, with show_query() added so users can inspect what actually gets sent. Recent releases show the constraint shifting from R-side translation to SQL dialect compatibility — the bugs now are about what a specific database will accept, not whether a model can be expressed. estimate_orbital_size() in 0.5.1 acknowledges the other practical limit, since generated expressions can grow large enough to matter before you generate them.
With the major boosting and ensemble engines covered, expect the next releases to keep chasing dialect-specific SQL correctness across warehouses rather than adding model families.
slider provides sliding-window and index-aware window functions for R, with a C implementation underneath and a specialised fast path for common aggregations. The user-facing surface has been stable since 0.3.0 in late 2022. Everything after that is compliance and platform work: STRING_PTR removed in 0.3.2, OBJECT() removed in 0.3.3, a vctrs callable's C signature corrected, and the minimum R version raised twice.
Two forces set the release schedule, and neither is feature demand. The first is CRAN closing off non-API C entry points, which packages reaching into R internals for speed have to unwind one accessor at a time — slider is on its second such release with no visible loss of function. The second is vctrs, whose breaking changes slider absorbs ahead of time; 0.2.2 exists solely to prepare for one. The last release that added anything callers can see was 0.3.0's slider_plus() and slider_minus() extension hooks.
Expect the pattern to continue: another non-API accessor removal or a vctrs compatibility release, rather than new window functions. The C-level surface is the only part of this package still moving.
Other Analytics 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 orbital or slider.
The clinical-report table engine learned Chinese, then learned to leave RTF entirely
New stewardship at openpharma, then two releases adding the methods MCP-Mod was missing
The stubbing library added httr2 support, then spent a year cutting itself free of everything else
crul took mocking back from webmockr and made it a property of the client itself
Six releases, six identical bodies — the feed carries the package abstract instead of release notes
chattr deleted every LLM integration it had written and outsourced the lot to ellmer
See all orbital alternatives → · See all slider alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. orbital and slider 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. orbital and slider 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 Analytics products to evaluate alongside.
Top orbital alternatives in Analytics are ranked by recent ship velocity. Browse the "orbital alternatives" section above for the current picks, or visit /alternatives/orbital for the full list with editorial commentary on each.
Top slider alternatives in Analytics are ranked by recent ship velocity. Browse the "slider alternatives" section above for the current picks, or visit /alternatives/slider for the full list with editorial commentary on each.