r2rtf
The clinical-report table engine learned Chinese, then learned to leave RTF entirely
A side-by-side editorial comparison of brulee and sparsevctrs — release velocity, themes, recent moves, and the top alternatives to consider.
tidymodels' torch backend grew from MLPs into a tabular deep learning suite with foundation models.
brulee fits neural networks for tidymodels on torch, and 1.0.0 redefined what that means: alongside the original MLP it now ships Regularization Learning Networks, ResNet with skip connections and batch normalization, AutoInt with columnwise attention, SAINT with row and column attention, and Chronos2, a foundational forecasting model. GPU acceleration arrived in the same release with automatic CUDA selection and opt-in MPS. Version 1.1.0 added TabICL, an open-source tabular foundation model, and 1.1.1 spent its time cleaning up the consequences of shipping models that need weight downloads.
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.
brulee fits neural networks for tidymodels on torch, and 1.0.0 redefined what that means: alongside the original MLP it now ships Regularization Learning Networks, ResNet with skip connections and batch normalization, AutoInt with columnwise attention, SAINT with row and column attention, and Chronos2, a foundational forecasting model. GPU acceleration arrived in the same release with automatic CUDA selection and opt-in MPS. Version 1.1.0 added TabICL, an open-source tabular foundation model, and 1.1.1 spent its time cleaning up the consequences of shipping models that need weight downloads.
The package has crossed from a torch convenience wrapper into a catalog of current tabular architectures, and the recent releases show it absorbing what that costs. Pretrained weights meant a 400MB download, so 1.1.1 stopped fetching them on attach and moved the cache to the platform-appropriate R_user_dir location. Numerical robustness is the other constant thread — 64-bit tensors, Gaussian initialization, gradient clipping extended architecture by architecture, and a ResNet batch-normalization bug where a single-row trailing batch produced all-NA predictions.
Gradient clipping has been rolled out one architecture at a time and TabICL is the newest arrival, so the likely next step is bringing the foundation models to parity with the trained ones on device selection, prediction types, and the tuning surface.
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 brulee 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 brulee alternatives → · See all sparsevctrs alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — tidymodels — within Analytics. brulee 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. brulee 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 brulee alternatives in Analytics are ranked by recent ship velocity. Browse the "brulee alternatives" section above for the current picks, or visit /alternatives/brulee 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.