discrim
discrim settled into a thin engine shim after handing its model definitions to parsnip.
A side-by-side editorial comparison of dbplyr and leaflet — release velocity, themes, recent moves, and the top alternatives to consider.
dbplyr ends its two-year backend migration by dropping 1st edition support outright
dbplyr translates dplyr code into SQL, and 2.6.0 closes a migration that has been running since 2023: first-edition backends no longer work at all. The same release converts a long list of soft deprecations into hard failures and removes functions deprecated as far back as 2019. The releases before it were translation-quality work across SQL Server, Redshift, Snowflake, Postgres, Spark and Teradata.
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.
dbplyr translates dplyr code into SQL, and 2.6.0 closes a migration that has been running since 2023: first-edition backends no longer work at all. The same release converts a long list of soft deprecations into hard failures and removes functions deprecated as far back as 2019. The releases before it were translation-quality work across SQL Server, Redshift, Snowflake, Postgres, Spark and Teradata.
The package is trading compatibility surface for a smaller, more consistent core it can actually evolve — qualified table names were overhauled in 2.5.0, sql() and ident() were refactored internally, and the cte argument gave way to a single sql_options() entry point. Backend breadth keeps growing at the translation level even as the extension API narrows.
With the edition split finally gone, expect the next cycle to spend its budget on dialect translations and the newer Spark/Databricks path rather than on further deprecation.
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 dbplyr or leaflet.
discrim settled into a thin engine shim after handing its model definitions to parsnip.
dbparser shed its database and CSV writers to become just a DrugBank parser.
desirability2 is making multi-metric model selection a first-class tidymodels step.
crosstalk is frozen infrastructure: four releases in five years, mostly CRAN upkeep.
cmdstanr keeps adding fast approximations beside full HMC, and fighting Windows toolchains.
comtradr's 1.0 line is a long tail of patches against a brittle UN trade API.
See all dbplyr 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. dbplyr 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. dbplyr 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 dbplyr alternatives in Analytics are ranked by recent ship velocity. Browse the "dbplyr alternatives" section above for the current picks, or visit /alternatives/dbplyr 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.