rsample
tidymodels' resampling package is retiring its old splitters for sliding windows.
A side-by-side editorial comparison of mlr3 and parsnip — release velocity, themes, recent moves, and the top alternatives to consider.
mlr3 is hardening the seams where its abstractions meet real learners
Releases arrive every few weeks and read as a systematic audit of the Learner interface. Recent versions added a native_model binding and a predict_raw flag so users can reach the underlying package's model and raw prediction, gave encapsulated learners a wall-clock deadline alongside the existing timeout, and removed the deprecated Task$divide(). A run of fixes addresses correctness at the boundary - factor level ordering that inverted binary probabilities, fallback learners losing state, misaligned probability columns.
parsnip added a whole new regression type, then wired R models to JAX and PyTorch
The package is expanding what tidymodels can express. Version 1.5.0 introduced ordinal_reg() as a new model type with three engines and its own link parameters, and added xgboost and qrnn engines for quantile regression. Version 1.6.0 followed with a keras3 engine for four model types, reaching Keras v3's TensorFlow, JAX and PyTorch backends. Around those, releases have been tuning-parameter range adjustments and engine-specific fixes.
Releases arrive every few weeks and read as a systematic audit of the Learner interface. Recent versions added a native_model binding and a predict_raw flag so users can reach the underlying package's model and raw prediction, gave encapsulated learners a wall-clock deadline alongside the existing timeout, and removed the deprecated Task$divide(). A run of fixes addresses correctness at the boundary - factor level ordering that inverted binary probabilities, fallback learners losing state, misaligned probability columns.
The framework is maturing from wrapping models to being accountable for what happens when wrapping goes wrong. Structured Mlr3Error and Mlr3Warning classes, conditions stored on the learner log, and messages replaced by conditions all point at making failures programmatically inspectable rather than printed. In parallel, escape hatches to the upstream model are being formalised instead of left to users digging into internals.
Expect the remaining deprecated surface to follow Task$divide() out, and further work on encapsulation and fallback behaviour, which is where most recent fixes have clustered. The raw and native_model accessors suggest more of the upstream model will be surfaced deliberately.
The package is expanding what tidymodels can express. Version 1.5.0 introduced ordinal_reg() as a new model type with three engines and its own link parameters, and added xgboost and qrnn engines for quantile regression. Version 1.6.0 followed with a keras3 engine for four model types, reaching Keras v3's TensorFlow, JAX and PyTorch backends. Around those, releases have been tuning-parameter range adjustments and engine-specific fixes.
Growth is happening on two axes: new modelling tasks that previously had no unified interface, and new engines behind tasks that already did. Both push in the same direction - a modeller specifies the model once and swaps the computational backend underneath, which is the whole premise parsnip is built on. The defunct surv_reg() shows old spellings being retired as that surface settles.
Expect further engines behind ordinal_reg() and quantile regression now that both have a home, and continued retirement of deprecated function names. The keras3 engine's multi-backend design is the obvious candidate to spread to more model types.
Other ai-assistants 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 mlr3 or parsnip.
tidymodels' resampling package is retiring its old splitters for sliding windows.
tidymodels' preprocessing engine learned sparsity, then settled into deprecations.
The resampling companion to scikit-learn now ships mostly to stay compatible with it.
Mem0 splits agent memory from user memory, then spends a week hardening the plumbing
Every post is a comparison page, and Pictory is always the answer.
DocsBot now lets an AI agent administer DocsBot, not just answer with it
See all mlr3 alternatives → · See all parsnip alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — r — within ai-assistants. mlr3 and parsnip 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. mlr3 and parsnip 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 ai-assistants products to evaluate alongside.
Top mlr3 alternatives in ai-assistants are ranked by recent ship velocity. Browse the "mlr3 alternatives" section above for the current picks, or visit /alternatives/mlr3 for the full list with editorial commentary on each.
Top parsnip alternatives in ai-assistants are ranked by recent ship velocity. Browse the "parsnip alternatives" section above for the current picks, or visit /alternatives/parsnip for the full list with editorial commentary on each.