pins
pins keeps adding a storage backend per release while retiring its original API
A side-by-side editorial comparison of embed and sparklyr — 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.
sparklyr now spends its releases absorbing dbplyr changes and feeding pysparklyr
sparklyr connects R to Spark, and almost nothing in this window originates inside the package. Releases restore compatibility after dbplyr changes its SQL generation, adapt to Spark 4.0 and to R 4.4's version-comparison changes, and convert functions into S3 methods so pysparklyr can supply its own implementations.
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.
sparklyr connects R to Spark, and almost nothing in this window originates inside the package. Releases restore compatibility after dbplyr changes its SQL generation, adapt to Spark 4.0 and to R 4.4's version-comparison changes, and convert functions into S3 methods so pysparklyr can supply its own implementations.
Two dependencies set the agenda. dbplyr repeatedly changes identifier quoting and lazy-table internals, and each change costs sparklyr a release. Meanwhile the package is being hollowed into a backend: ml_fit(), spark_apply(), spark_write_delta() and now tune_grid_spark() exist as methods so that pysparklyr, the Databricks Connect path, can override them. Dependency removal - tibble, rappdirs, digest - runs alongside as the package slims down.
Expect the next releases to continue tracking dbplyr and Spark versions, and more functions to be converted to methods as functionality shifts toward pysparklyr; new capability arriving in sparklyr itself looks unlikely.
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 sparklyr.
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 sparklyr 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 sparklyr 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 sparklyr 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 sparklyr alternatives in Analytics are ranked by recent ship velocity. Browse the "sparklyr alternatives" section above for the current picks, or visit /alternatives/sparklyr for the full list with editorial commentary on each.