r2rtf
The clinical-report table engine learned Chinese, then learned to leave RTF entirely
A side-by-side editorial comparison of bundle and tabnet — release velocity, themes, recent moves, and the top alternatives to consider.
Four releases in three years, each one teaching the serializer about a model type it couldn't carry
bundle solves a narrow, real problem: many R model objects hold pointers to external state — compiled boosters, Java handles, torch tensors — that do not survive being saved and reloaded in another session. It wraps them so they do. The package has shipped four releases since 2022, and the shape of each is the same: extend coverage to another model class, or repair coverage that an upstream release broke.
A tabular deep-learning model in R that keeps widening what counts as a tabular task.
tabnet ports the TabNet attentive tabular architecture to R on torch, wired into tidymodels through parsnip so it slots into workflows, tuning, and case weights like any other engine. The model surface has grown well past plain supervised fitting: unsupervised pretraining, missing values in predictors, multi-outcome fitting, hierarchical multi-label classification, and built-in explainability via tabnet_explain(). The 0.9.x line has been consolidating rather than adding, with 0.9.0 finally making hierarchical classification work correctly by accounting for the ancestor matrix.
bundle solves a narrow, real problem: many R model objects hold pointers to external state — compiled boosters, Java handles, torch tensors — that do not survive being saved and reloaded in another session. It wraps them so they do. The package has shipped four releases since 2022, and the shape of each is the same: extend coverage to another model class, or repair coverage that an upstream release broke.
Coverage is the product, so the release cadence is set by the ecosystem rather than by a roadmap. dbarts arrived in 0.1.2, along with extra work to preserve xgboost's nfeatures and feature_names through a round trip; 0.1.3 exists because xgboost changed its model format again. The 0.1.1 fix — recipes steps nested inside workflows — points at the same underlying issue one level up, where the object needing bundling is buried inside a tidymodels pipeline rather than passed directly.
Expect the next release to follow the same trigger: either a new parsnip engine that carries external pointers, or another upstream format change in one of the engines already covered. xgboost has now forced two of the four releases.
tabnet ports the TabNet attentive tabular architecture to R on torch, wired into tidymodels through parsnip so it slots into workflows, tuning, and case weights like any other engine. The model surface has grown well past plain supervised fitting: unsupervised pretraining, missing values in predictors, multi-outcome fitting, hierarchical multi-label classification, and built-in explainability via tabnet_explain(). The 0.9.x line has been consolidating rather than adding, with 0.9.0 finally making hierarchical classification work correctly by accounting for the ancestor matrix.
Two threads run through the release history. The first is task surface — each minor version tends to admit a class of problem the model previously could not express, from missing data to hierarchy to imbalanced binary outcomes. The second is torch-level performance and correctness, visible in the torch_ignite_adam default that cut pretraining time roughly 30% and the fix for optimizers frozen after checkpointing on cuda and mps. Tidymodels integration is treated as a first-class obligation, with parsnip breaking changes tracked release by release.
The hierarchical path is the least finished: 0.5.0 introduced it and 0.9.0 only just made it effective, so the next releases most likely extend evaluation and explainability to hierarchical fits rather than adding another task type.
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 bundle or tabnet.
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 bundle alternatives → · See all tabnet alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — tidymodels — within Analytics. tabnet is currently shipping more aggressively (velocity 2.5 vs 0.0), with 0 editorial sparks in the last 30 days against 0. 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. tabnet is currently shipping more aggressively (velocity 2.5 vs 0.0), with 0 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other Analytics products to evaluate alongside.
Top bundle alternatives in Analytics are ranked by recent ship velocity. Browse the "bundle alternatives" section above for the current picks, or visit /alternatives/bundle for the full list with editorial commentary on each.
Top tabnet alternatives in Analytics are ranked by recent ship velocity. Browse the "tabnet alternatives" section above for the current picks, or visit /alternatives/tabnet for the full list with editorial commentary on each.