pins
pins keeps adding a storage backend per release while retiring its original API
A side-by-side editorial comparison of dtplyr and leaflet — release velocity, themes, recent moves, and the top alternatives to consider.
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.
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.
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.
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.
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.
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 dtplyr 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 dtplyr 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. dtplyr 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. dtplyr 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 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.
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.