pins
pins keeps adding a storage backend per release while retiring its original API
A side-by-side editorial comparison of embed and insight — release velocity, themes, recent moves, and the top alternatives to consider.
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.
insight quietly widens the set of model objects the easystats ecosystem can read
insight is the extraction layer under the easystats packages — it answers what a fitted model's parameters, data, variance and priors are, for whatever object it is handed. The 1.4.x and 1.5.x releases read as a steady widening of that support list: tidymodels workflows, cmdstanr fits, rstpm2 survival models, lavaan variance-covariance, mice imputations.
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.
insight is the extraction layer under the easystats packages — it answers what a fitted model's parameters, data, variance and priors are, for whatever object it is handed. The 1.4.x and 1.5.x releases read as a steady widening of that support list: tidymodels workflows, cmdstanr fits, rstpm2 survival models, lavaan variance-covariance, mice imputations.
Two things move together here. The support list grows toward objects produced outside the easystats world, and performance work targets the helpers that everything else calls — compact_list(), is_empty_object(), find_parameters() on mgcv models. New functions appear occasionally (get_simulated(), vcovFPC()) but the center of gravity is coverage, not capability.
Expect further model classes to be added as downstream easystats packages need them, and continued alignment with R-devel behavior changes like the weighted-residuals revision.
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 embed or insight.
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
See all embed alternatives → · See all insight alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. embed and insight 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. embed and insight 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 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.
Top insight alternatives in Analytics are ranked by recent ship velocity. Browse the "insight alternatives" section above for the current picks, or visit /alternatives/insight for the full list with editorial commentary on each.