recipes
tidymodels' preprocessing engine learned sparsity, then settled into deprecations.
A side-by-side editorial comparison of mlr3 and rsample — 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.
tidymodels' resampling package is retiring its old splitters for sliding windows.
rsample is at 1.3.2, a small release covering spatialsample interoperability and a soft deprecation of the lag argument on initial_time_split(). The more consequential work sits behind it: 1.3.1 added internal_calibration_split() and a calibration() accessor so tune can fit a preprocessor and a post-processor on separate parts of the analysis set, and 1.3.0 superseded rolling_origin() with the sliding_* family.
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.
rsample is at 1.3.2, a small release covering spatialsample interoperability and a soft deprecation of the lag argument on initial_time_split(). The more consequential work sits behind it: 1.3.1 added internal_calibration_split() and a calibration() accessor so tune can fit a preprocessor and a post-processor on separate parts of the analysis set, and 1.3.0 superseded rolling_origin() with the sliding_* family.
Two threads run through the window. Time-based resampling is migrating from rolling_origin() to sliding_window(), sliding_index() and sliding_period(), while validation_split() and its relatives have moved from soft deprecation to warning in favour of the three-way initial_validation_split(). Alongside that, rsample is growing infrastructure other tidymodels packages consume rather than user-facing splitters.
Given that validation_split() and friends now warn and initial_time_split()'s lag argument is soft-deprecated, the next release most likely escalates those deprecations rather than adding a resampling scheme.
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 rsample.
tidymodels' preprocessing engine learned sparsity, then settled into deprecations.
The resampling companion to scikit-learn now ships mostly to stay compatible with it.
parsnip added a whole new regression type, then wired R models to JAX and PyTorch
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 rsample alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. mlr3 and rsample 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 rsample 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 rsample alternatives in ai-assistants are ranked by recent ship velocity. Browse the "rsample alternatives" section above for the current picks, or visit /alternatives/rsample for the full list with editorial commentary on each.