easystats
The easystats meta-package is install tooling wrapped around a relicensed ecosystem.
A side-by-side editorial comparison of bbotk and pins — release velocity, themes, recent moves, and the top alternatives to consider.
bbotk is generalizing from an optimizer toolkit into an evaluation framework.
bbotk is the black-box optimization backend behind mlr3 tuning: search spaces, terminators, archives, and an async layer built on rush. Recent releases pair steady async-API buildout with removal of the deprecated arguments that preceded it. The 1.9.0 release introduced EvalInstance as a base class for OptimInstance, separating evaluating an objective from optimizing one.
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.
bbotk is the black-box optimization backend behind mlr3 tuning: search spaces, terminators, archives, and an async layer built on rush. Recent releases pair steady async-API buildout with removal of the deprecated arguments that preceded it. The 1.9.0 release introduced EvalInstance as a base class for OptimInstance, separating evaluating an objective from optimizing one.
Two threads run through the visible history. The first is async optimization maturing: ArchiveAsync gained a full push/finish/fail vocabulary over rush tasks in 1.11.0, and 1.12.0 deleted the deprecated extra arguments it replaced. The second is dependency consolidation, with custom C hypervolume code handed to moocore and rush pinned to 1.0.0, trimming maintenance surface as the async path becomes the default.
The deprecation removals in 1.12.0 suggest the async archive API is now treated as settled; the next releases most likely build on EvalInstance rather than continuing to churn ArchiveAsync.
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 bbotk 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.
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. bbotk is currently shipping more aggressively (velocity 2.5 vs 0.0), with 0 editorial sparks in the last 30 days against 0. 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. bbotk is currently shipping more aggressively (velocity 2.5 vs 0.0), with 0 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other Analytics products to evaluate alongside.
Top bbotk alternatives in Analytics are ranked by recent ship velocity. Browse the "bbotk alternatives" section above for the current picks, or visit /alternatives/bbotk 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.