pins
pins keeps adding a storage backend per release while retiring its original API
Comparison · Analytics
dtplyr vs embed
A side-by-side editorial comparison of dtplyr and embed — release velocity, themes, recent moves, and the top alternatives to consider.
dtplyr vs embed: at a glance
What is dtplyr?
dtplyr stopped hijacking data.table objects and became an opt-in translator
dtplyr converts dplyr and tidyr code into data.table syntax, and 1.3.0 redrew its boundary: verbs no longer dispatch to dtplyr translations just because dtplyr is loaded, so lazy_dt() has to be called explicitly. Since then the work has been translation coverage — reframe(), case_match(), consecutive_id() — plus a long tail of correctness fixes in grouping and .by.
What is embed?
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.
dtplyr vs embed: editorial side-by-side
dtplyr
0.0ANALYTICS
dtplyr stopped hijacking data.table objects and became an opt-in translator
◆ Current state
dtplyr converts dplyr and tidyr code into data.table syntax, and 1.3.0 redrew its boundary: verbs no longer dispatch to dtplyr translations just because dtplyr is loaded, so lazy_dt() has to be called explicitly. Since then the work has been translation coverage — reframe(), case_match(), consecutive_id() — plus a long tail of correctness fixes in grouping and .by.
◆ Where it's heading
The package is trailing dplyr's own feature releases rather than leading them, adding each new verb once it settles upstream. Performance work is targeted at specific verbs where data.table has a faster primitive: setorder() for arrange(), reference drops for select(), rleid() for consecutive_id(). Release cadence has thinned considerably since 2023.
◆ Prediction
Expect further one-for-one translations as dplyr adds verbs, and continued fixes around .by and non-standard column names; the entries show no sign of a broader redesign.
embed
0.0ANALYTICS
embed keeps adding encoding steps while shedding its deep-learning dependencies
◆ Current state
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.
◆ Where it's heading
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.
◆ Prediction
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.
Alternatives to dtplyr and embed
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 dtplyr or embed.
tsibble
tsibble shipped one release in five and a half years - the data structure is finished
yardstick
yardstick made fairness metrics a first-class part of tidymodels evaluation
tune
tune extends tuning past the model itself to postprocessors, and adds a second parallel backend
leaflet
leaflet relicensed to MIT and finished migrating off R's retired spatial stack
ggpubr
ggpubr reached 1.0.0 with p-value formatting presets for specific journals
See all dtplyr alternatives → · See all embed alternatives →
Recent activity from dtplyr and embed
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 6mo agoembedstep_umap() zero-component bug fixed
- 8mo agoembedCompatibility with all xgboost versions
- 11mo agodtplyrreframe(), case_match() and consecutive_id() gain translations
- 11mo agoembedstep_lencode() adds analytical likelihood encoding with pooling
- 1y agoembedUMAP initial and target_weight become tunable
- 2y agoembedkeras and tensorflow moved to Suggests
- 2y agoembedstep_collapse_stringdist() returns factors
- 3y agodtplyrcrayon dependency dropped
- 3y agodtplyrVerbs stop auto-dispatching; lazy_dt() now required ⚡
- 3y agodtplyrdtplyr 1.2.2
- 4y agodtplyrdtplyr 1.2.1
- 4y agodtplyrEight tidyr verbs gain data.table translations
Frequently asked questions
What is the difference between dtplyr and embed?
They serve adjacent needs but don't currently overlap on shipped themes. dtplyr 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.
Is dtplyr better than embed?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. dtplyr 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.
What are the best alternatives to dtplyr?
Top dtplyr alternatives in Analytics are ranked by recent ship velocity. Browse the "dtplyr alternatives" section above for the current picks, or visit /alternatives/dtplyr for the full list with editorial commentary on each.
What are the best alternatives to embed?
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.