easystats
The easystats meta-package is install tooling wrapped around a relicensed ecosystem.
A side-by-side editorial comparison of bbotk and see — 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.
see grows wherever easystats adds a diagnostic, one plot method at a time.
see is the visualization layer for the easystats ecosystem, supplying plot() methods for performance, parameters and datawizard objects. Each release adds methods for whatever those packages shipped — prior predictive checks, DAG diagrams, factor-analysis graphs — alongside steady theme and geom refinement.
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.
see is the visualization layer for the easystats ecosystem, supplying plot() methods for performance, parameters and datawizard objects. Each release adds methods for whatever those packages shipped — prior predictive checks, DAG diagrams, factor-analysis graphs — alongside steady theme and geom refinement.
Growth here is downstream-driven rather than self-directed: see expands to cover new diagnostics as easystats produces them. Running alongside that is a sustained investment in presentation control — theme arguments on plot methods, elements that scale with base_size — which suits users embedding these plots in documents rather than glancing at them interactively.
Expect new plot methods to keep arriving in step with performance and parameters releases, with continued theming work rather than any change in the package's scope.
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 see.
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 see alternatives in Analytics are ranked by recent ship velocity. Browse the "see alternatives" section above for the current picks, or visit /alternatives/see-r for the full list with editorial commentary on each.