pins
pins keeps adding a storage backend per release while retiring its original API
A side-by-side editorial comparison of embed and leaflet — 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.
leaflet relicensed to MIT and finished migrating off R's retired spatial stack
leaflet is the R binding for the Leaflet mapping library. Its recent releases are dominated by one long migration: away from sp, rgdal, rgeos and raster, and toward sf and terra. Version 2.2.3 completed the user-facing half of that - sp is no longer installed by default, and bundled datasets ship as sf objects - while also relicensing the package from GPL-2 to MIT.
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.
leaflet is the R binding for the Leaflet mapping library. Its recent releases are dominated by one long migration: away from sp, rgdal, rgeos and raster, and toward sf and terra. Version 2.2.3 completed the user-facing half of that - sp is no longer installed by default, and bundled datasets ship as sf objects - while also relicensing the package from GPL-2 to MIT.
This is a package being brought into line with an ecosystem that changed underneath it. The retirement of rgdal and rgeos forced the terra and sf work; the license change and dependency reductions are the maintainers taking the opportunity to clean up while they are already in there. Feature work, such as the full viridisLite palette set, arrives as a side effect of the tidying.
With the sp path now opt-in and the retired geospatial dependencies gone, expect the remaining work to be small: palette and provider-tile handling, and keeping the bundled JavaScript current.
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 leaflet.
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
ggpubr reached 1.0.0 with p-value formatting presets for specific journals
bigrquery went MIT, then handed its slowest path to the BigQuery Storage API
See all embed alternatives → · See all leaflet 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 leaflet 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 leaflet 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 leaflet alternatives in Analytics are ranked by recent ship velocity. Browse the "leaflet alternatives" section above for the current picks, or visit /alternatives/leaflet-r for the full list with editorial commentary on each.