← Back to home
Comparison · ai-assistants

recipes vs Transformers

A side-by-side editorial comparison of recipes and Transformers — release velocity, themes, recent moves, and the top alternatives to consider.

recipes vs Transformers: at a glance

FeaturerecipesTransformers
Sectorai-assistantsai-assistants
Velocity score0.06.3
Sparks · 30d01
Top themestidymodels, preprocessing, sparse-data, deprecationskernel-dispatch, breaking-changes, vllm-backend, day-0-models
Last editorial update1h ago1d ago
WebsiteVisit →Visit →

What is recipes?

tidymodels' preprocessing engine learned sparsity, then settled into deprecations.

recipes is at 1.3.3, whose entire changelog is one suggested-package declaration. The substantive release in the window is 1.2.0, which taught recipe, prep and bake to work with sparse tibbles and sparse matrices, added a sparse argument to eight dummy and indicator steps, and made seventeen more steps preserve sparsity they receive. Since then the work has been deprecations and bug fixes.

Read the full recipes trajectory →

What is Transformers?

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.

Read the full Transformers trajectory →

recipes vs Transformers: editorial side-by-side

R
recipes
AI-ASSISTANTS
0.0

tidymodels' preprocessing engine learned sparsity, then settled into deprecations.

◆ Current state

recipes is at 1.3.3, whose entire changelog is one suggested-package declaration. The substantive release in the window is 1.2.0, which taught recipe, prep and bake to work with sparse tibbles and sparse matrices, added a sparse argument to eight dummy and indicator steps, and made seventeen more steps preserve sparsity they receive. Since then the work has been deprecations and bug fixes.

◆ Where it's heading

The direction is consolidation of a large step catalogue rather than growth. step_select and step_nnmf have entered deprecation, arguments across nine steps moved from strings and vars() calls to bare names, and all steps now require the same four arguments. The sparse work stands as the last structural change; what follows tidies the surface around it.

◆ Prediction

With step_select mid-deprecation and step_nnmf newly deprecated in favour of step_nnmf_sparse, the next release most likely advances those deprecations rather than adding steps.

T
Transformers
AI-ASSISTANTS
6.3

Transformers is becoming a kernel-dispatch layer, and it's breaking APIs to get there

◆ Current state

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.

◆ Where it's heading

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.

◆ Prediction

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.

Alternatives to recipes and Transformers

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 recipes or Transformers.

See all recipes alternatives → · See all Transformers alternatives →

Recent activity from recipes and Transformers

Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.

  1. 2d agoTransformersKernels go opt-in as T5 and linear attention move to shared backends
  2. 27d agoTransformersPatch fixes Inkling prefill and assisted-decoding cache bugs
  3. 27d agoTransformersInkling lands day-0; GPTNeoX and GPTBigCode realign for vLLM
  4. 1mo agoTransformersPatch unblocks the latest vLLM release
  5. 1mo agoTransformersKimi K2.5-2.7 and MiMo-V2-Flash architectures added
  6. 1mo agoTransformersPatch raises PEFT floor and fixes Mistral tokenizer resolution
  7. 2mo agorecipesDeclares mixOmics as a suggested package
  8. 4mo agorecipesstep_nnmf() deprecated in favour of step_nnmf_sparse()
  9. 1y agorecipesFixes tune_args() with tuned parsnip arguments
  10. 1y agorecipesBare-name arguments across nine steps; step_select() deprecated
  11. 1y agorecipesFixes sparsity steps applied to derived variables
  12. 1y agorecipesSparse tibbles and sparse matrices supported end to end

Frequently asked questions

What is the difference between recipes and Transformers?

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.

Is recipes better than Transformers?

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.

What are the best alternatives to recipes?

Top recipes alternatives in ai-assistants are ranked by recent ship velocity. Browse the "recipes alternatives" section above for the current picks, or visit /alternatives/recipes for the full list with editorial commentary on each.

What are the best alternatives to Transformers?

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.