pins
pins keeps adding a storage backend per release while retiring its original API
A side-by-side editorial comparison of bigrquery and censored — 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.
censored keeps survival models aligned with parsnip's shifting prediction contracts
censored supplies survival-analysis engines to parsnip, and its release history is dominated by staying in step with the rest of tidymodels rather than shipping independent features. The 0.2.0 and 0.3.0 releases added engines and prediction types; everything since has been contract alignment — quantile prediction format, hardhat test adaptation, flexsurv preparation.
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.
censored supplies survival-analysis engines to parsnip, and its release history is dominated by staying in step with the rest of tidymodels rather than shipping independent features. The 0.2.0 and 0.3.0 releases added engines and prediction types; everything since has been contract alignment — quantile prediction format, hardhat test adaptation, flexsurv preparation.
The package is settling into a downstream role where parsnip and hardhat set the interface and censored implements it for censored regression. Breaking changes arrive from upstream, not from new ideas here. The substantive engine work — aorsf, flexsurvspline, glmnet multi_predict — is behind it, and recent cycles are thin.
Expect the next releases to track further parsnip prediction-type changes rather than add engines; the entries do not show new survival methods in progress.
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 censored.
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
leaflet relicensed to MIT and finished migrating off R's retired spatial stack
ggpubr reached 1.0.0 with p-value formatting presets for specific journals
See all bigrquery alternatives → · See all censored 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 censored 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 censored 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 censored alternatives in Analytics are ranked by recent ship velocity. Browse the "censored alternatives" section above for the current picks, or visit /alternatives/censored for the full list with editorial commentary on each.