pins
pins keeps adding a storage backend per release while retiring its original API
A side-by-side editorial comparison of dials and embed — release velocity, themes, recent moves, and the top alternatives to consider.
dials is quietly registering the tuning parameters for tidymodels' deep-learning push
dials defines the parameter objects and grid constructors that tidymodels tunes over, which makes its release notes a reliable early read on what the rest of the stack is about to support. The last two releases are dominated by attention-model parameters — SAINT and tabular deep learning via brulee, TabPFN via parsnip's tab_pfn() — alongside catboost parameters for bonsai and calibration parameters for tailor.
embed keeps adding encoding steps while shedding its deep-learning dependencies
embed supplies recipes steps that turn categorical predictors into numeric representations — likelihood encoding, UMAP projection, string-distance collapsing. The 1.1.x line made UMAP arguments tunable and moved keras and tensorflow out of hard dependencies; 1.2.0 added analytical likelihood encoding with partial pooling and retired step_feature_hash() in favor of textrecipes.
dials defines the parameter objects and grid constructors that tidymodels tunes over, which makes its release notes a reliable early read on what the rest of the stack is about to support. The last two releases are dominated by attention-model parameters — SAINT and tabular deep learning via brulee, TabPFN via parsnip's tab_pfn() — alongside catboost parameters for bonsai and calibration parameters for tailor.
The grid machinery itself is settled: grid_space_filling() consolidated the older designs, and the grid_*() functions now error rather than warn on the wrong size argument. What keeps moving is the parameter catalog, and it is moving toward neural and foundation-model territory that tidymodels historically left alone. Error-message quality is a steady secondary theme.
Expect further parameter objects to land ahead of the parsnip and brulee releases that use them — the attention and tabular-foundation-model work in flight is the clearest thing the entries point to.
embed supplies recipes steps that turn categorical predictors into numeric representations — likelihood encoding, UMAP projection, string-distance collapsing. The 1.1.x line made UMAP arguments tunable and moved keras and tensorflow out of hard dependencies; 1.2.0 added analytical likelihood encoding with partial pooling and retired step_feature_hash() in favor of textrecipes.
Two quiet directions run through these releases. One is making the steps tunable rather than fixed, so they participate properly in tidymodels grids. The other is boundary maintenance: heavy dependencies pushed to Suggests, overlapping steps handed to the package that owns them. Recent releases are thin and fix-driven.
Expect further consolidation with textrecipes over which package owns which encoding step, and continued upkeep against xgboost and uwot releases rather than new step families.
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 dials or embed.
pins keeps adding a storage backend per release while retiring its original API
tsibble shipped one release in five and a half years - the data structure is finished
yardstick made fairness metrics a first-class part of tidymodels evaluation
tune extends tuning past the model itself to postprocessors, and adds a second parallel backend
leaflet relicensed to MIT and finished migrating off R's retired spatial stack
ggpubr reached 1.0.0 with p-value formatting presets for specific journals
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — tidymodels — within Analytics. dials and embed 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. dials and embed 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 Analytics products to evaluate alongside.
Top dials alternatives in Analytics are ranked by recent ship velocity. Browse the "dials alternatives" section above for the current picks, or visit /alternatives/dials for the full list with editorial commentary on each.
Top embed alternatives in Analytics are ranked by recent ship velocity. Browse the "embed alternatives" section above for the current picks, or visit /alternatives/embed for the full list with editorial commentary on each.