easystats
The easystats meta-package is install tooling wrapped around a relicensed ecosystem.
A side-by-side editorial comparison of bigrquery and dbparser — release velocity, themes, recent moves, and the top alternatives to consider.
bigrquery went MIT, then handed its slowest path to the BigQuery Storage API
bigrquery is the R client for Google BigQuery. Version 1.5.0 was the structural release - MIT relicensing, removal of the long-deprecated non-bq_ API, and a move to the second edition of the dbplyr interface with a much fuller DBI implementation. Since then the work has been about the two things that hurt in practice: download throughput and cost visibility.
dbparser shed its database and CSV writers to become just a DrugBank parser.
dbparser reads DrugBank's XML release into R tibbles. Its 2.0 line removed the persistence features that defined 1.x, writing to a database or to CSV, in favour of returning a dvobject the caller handles. Releases since have been column-naming normalization and test updates against newer DrugBank versions.
bigrquery is the R client for Google BigQuery. Version 1.5.0 was the structural release - MIT relicensing, removal of the long-deprecated non-bq_ API, and a move to the second edition of the dbplyr interface with a much fuller DBI implementation. Since then the work has been about the two things that hurt in practice: download throughput and cost visibility.
The package is settling into being a well-behaved DBI and dbplyr backend rather than a bespoke API wrapper, and offloading its hard parts to specialist packages - clock for date parsing, bigrquerystorage for bulk downloads, gargle for auth. The recent additions read like responses to production use: job labels for cost allocation, microsecond timestamp precision, a configurable quiet option.
Expect bigrquerystorage to move from optional to expected for large reads, and further work on upload fidelity, where digits and timezone handling have needed repeated correction.
dbparser reads DrugBank's XML release into R tibbles. Its 2.0 line removed the persistence features that defined 1.x, writing to a database or to CSV, in favour of returning a dvobject the caller handles. Releases since have been column-naming normalization and test updates against newer DrugBank versions.
The arc is scope reduction. Version 1.2.0 was the high-water mark of ambition, adding collective parsers, an R6 redesign and progress bars; 2.0.1 then deprecated the database and CSV writers and the old public methods outright. What remains is a narrower package whose ongoing work is keeping column names consistent and tests current with DrugBank's schema.
The last two releases track DrugBank data versions rather than adding features, so the next is most likely another compatibility pass against a newer DrugBank release.
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 bigrquery or dbparser.
The easystats meta-package is install tooling wrapped around a relicensed ecosystem.
discrim settled into a thin engine shim after handing its model definitions to parsnip.
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 bigrquery alternatives → · See all dbparser alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. bigrquery and dbparser 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. bigrquery and dbparser 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 bigrquery alternatives in Analytics are ranked by recent ship velocity. Browse the "bigrquery alternatives" section above for the current picks, or visit /alternatives/bigrquery for the full list with editorial commentary on each.
Top dbparser alternatives in Analytics are ranked by recent ship velocity. Browse the "dbparser alternatives" section above for the current picks, or visit /alternatives/dbparser for the full list with editorial commentary on each.