recipes
tidymodels' preprocessing engine learned sparsity, then settled into deprecations.
A side-by-side editorial comparison of rsample and Transformers — release velocity, themes, recent moves, and the top alternatives to consider.
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.
Transformers is becoming a kernel-dispatch layer, and it's breaking APIs to get there
Transformers ships every two to four weeks on a split rhythm: minors carry day-0 architecture support for newly released open-weight models, patches almost exclusively unblock downstream serving runtimes. The last six releases added Meta's Muse Glimmer, Thinking Machines' Inkling, the Kimi K2.5 family and MiMo-V2-Flash, while three separate patches existed mainly to keep vLLM in sync. v5.15.0 breaks that pattern by landing four flagged breaking changes at once, including making kernel selection opt-in for linear attention models.
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.
Transformers ships every two to four weeks on a split rhythm: minors carry day-0 architecture support for newly released open-weight models, patches almost exclusively unblock downstream serving runtimes. The last six releases added Meta's Muse Glimmer, Thinking Machines' Inkling, the Kimi K2.5 family and MiMo-V2-Flash, while three separate patches existed mainly to keep vLLM in sync. v5.15.0 breaks that pattern by landing four flagged breaking changes at once, including making kernel selection opt-in for linear attention models.
The refactor visible across these releases is a consolidation onto shared attention and kernel dispatch: the T5 family moved onto ALL_ATTENTION_FUNCTIONS, every linear attention model was rewritten against one convolution standard, and Gemma 4's heterogeneous attention config was made explicit through per_layer_config. The release notes state outright that the kernels package will likely become a required dependency of transformers[torch]. Alongside that, the project is absorbing compatibility work on behalf of vLLM rather than its own direct users — weight remaps and attention-backend flags added specifically for the vLLM modelling backend.
Expect kernels to move from opt-in to a hard dependency of transformers[torch], with more model families migrated onto the shared attention backend path and the eager-only route treated as a fallback. Day-0 architecture additions continue at the current pace on every minor.
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 rsample or Transformers.
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
mlr3 is hardening the seams where its abstractions meet real learners
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.
See all rsample alternatives → · See all Transformers alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Transformers is currently shipping more aggressively (velocity 6.3 vs 0.0), with 1 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. Transformers is currently shipping more aggressively (velocity 6.3 vs 0.0), with 1 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other ai-assistants products to evaluate alongside.
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.
Top Transformers alternatives in ai-assistants are ranked by recent ship velocity. Browse the "Transformers alternatives" section above for the current picks, or visit /alternatives/transformers for the full list with editorial commentary on each.