mlr3mbo
mlr3mbo picked its defaults from a benchmark study, not from taste
A side-by-side editorial comparison of butcher and dbparser — release velocity, themes, recent moves, and the top alternatives to consider.
butcher expands from trimming models to trimming whole tidymodels workflows
butcher strips the parts of fitted R model objects that bloat serialized size without being needed for prediction, and it grows one method family at a time. The 0.3.x line piled up coverage for MASS, klaR, mixOmics, ipred, survival and xgboost objects; 0.4.0 changes the target from individual models to resampling and tuning containers, and hands maintenance to Max Kuhn.
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.
butcher strips the parts of fitted R model objects that bloat serialized size without being needed for prediction, and it grows one method family at a time. The 0.3.x line piled up coverage for MASS, klaR, mixOmics, ipred, survival and xgboost objects; 0.4.0 changes the target from individual models to resampling and tuning containers, and hands maintenance to Max Kuhn.
Coverage is following where tidymodels users actually accumulate size — rset, rsplit, tune_results and workflow_set objects are the things that get large in a tuning run, not single fits. The maintainer handoff points the package further into the tidymodels orbit rather than the broad model zoo it started as. Releases are otherwise small and fix-driven.
Expect further methods for tidymodels container classes and continued upkeep against xgboost and torch-backed engines; the entries show no move toward automatic size reporting or a different API.
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 butcher or dbparser.
mlr3mbo picked its defaults from a benchmark study, not from taste
loo keeps rewriting the diagnostics Bayesian modellers read off model comparison
mlr3fselect turned feature selection into an asynchronous, distributable job
lime survives on compatibility patches years after its research moment
mlr3measures is systematically retrofitting sample weights across every metric
mlr3cluster went from a handful of clusterers to covering the field
See all butcher 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. butcher 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. butcher 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 butcher alternatives in Analytics are ranked by recent ship velocity. Browse the "butcher alternatives" section above for the current picks, or visit /alternatives/butcher 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.