easystats
The easystats meta-package is install tooling wrapped around a relicensed ecosystem.
A side-by-side editorial comparison of bigrquery and pins — 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.
pins keeps adding a storage backend per release while retiring its original API
pins publishes and versions R objects to a board, where a board is whatever storage you have. The recent releases read as a steady list of new boards - Google Cloud Storage, Google Drive, Databricks Volumes, Connect vanity URLs - alongside serialization changes that track which formats R users actually want: parquet via nanoparquet, and qs replaced by qs2.
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.
pins publishes and versions R objects to a board, where a board is whatever storage you have. The recent releases read as a steady list of new boards - Google Cloud Storage, Google Drive, Databricks Volumes, Connect vanity URLs - alongside serialization changes that track which formats R users actually want: parquet via nanoparquet, and qs replaced by qs2.
Two long-running processes, neither dramatic. Backend coverage expands toward wherever teams already store artifacts, which increasingly means Databricks and cloud object storage rather than a shared drive. Meanwhile the legacy pin() API from before the board model has been in a staged deprecation across at least three releases, escalated each time rather than removed.
Expect another board or two as storage platforms are requested, and the legacy pin() functions to finally become errors; the format list will keep tracking whichever serializer the R community settles on.
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 pins.
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.
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.
See all bigrquery alternatives → · See all pins 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 pins 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 pins 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 pins alternatives in Analytics are ranked by recent ship velocity. Browse the "pins alternatives" section above for the current picks, or visit /alternatives/pins-r for the full list with editorial commentary on each.