r2rtf
The clinical-report table engine learned Chinese, then learned to leave RTF entirely
A side-by-side editorial comparison of orbital and sparsevctrs — 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.
Sparse vectors stopped being a storage trick and became something you can do arithmetic on
sparsevctrs supplies sparse vectors that live inside ordinary data frames and tibbles, which is what lets tidymodels carry wide, mostly-zero feature matrices without densifying them. Through 0.2.0 and 0.3.0 the package built out a computation layer on top of that storage — first summary statistics, then scalar and element-wise arithmetic — and everything since has been correctness work at the C level.
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.
sparsevctrs supplies sparse vectors that live inside ordinary data frames and tibbles, which is what lets tidymodels carry wide, mostly-zero feature matrices without densifying them. Through 0.2.0 and 0.3.0 the package built out a computation layer on top of that storage — first summary statistics, then scalar and element-wise arithmetic — and everything since has been correctness work at the C level.
The release pattern splits cleanly at 0.3.0. Before it, new functions arrive in batches; after it, five consecutive releases are bug fixes, and the bugs are the kind that come with hand-written sparse kernels: a stack imbalance when sparse_multiplication() returns all zeros, undefined behaviour in multiplication, type errors in sparse_is_na(), coercion failures on NA input. That is the expected cost of an ALTREP-backed numerical layer, and the fixes are landing steadily.
With the arithmetic surface in place and the recent releases all narrow fixes, the next one is more likely another correctness patch than a new function family. The R devel fix in 0.3.5 suggests upcoming R releases are the current source of breakage.
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 sparsevctrs.
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 sparsevctrs alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — tidymodels — within Analytics. orbital and sparsevctrs 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 sparsevctrs 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 sparsevctrs alternatives in Analytics are ranked by recent ship velocity. Browse the "sparsevctrs alternatives" section above for the current picks, or visit /alternatives/sparsevctrs for the full list with editorial commentary on each.