mlr3mbo
mlr3mbo picked its defaults from a benchmark study, not from taste
Comparison · Analytics
dbparser vs feasts
A side-by-side editorial comparison of dbparser and feasts — release velocity, themes, recent moves, and the top alternatives to consider.
dbparser vs feasts: at a glance
What is dbparser?
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.
What is feasts?
feasts is splitting itself in two, moving every plot into ggtime
feasts provides feature extraction and statistics for tsibble time series. The last two releases are dominated by one decision: all of its gg_*() plotting functions are being moved out into a separate ggtime package. 0.4.2 announced the deprecation and 0.5.0 makes ggtime a dependency with soft-deprecation messages on every re-export.
dbparser vs feasts: editorial side-by-side
dbparser
0.0ANALYTICS
dbparser shed its database and CSV writers to become just a DrugBank parser.
◆ Current state
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.
◆ Where it's heading
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.
◆ Prediction
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.
feasts
0.0ANALYTICS
feasts is splitting itself in two, moving every plot into ggtime
◆ Current state
feasts provides feature extraction and statistics for tsibble time series. The last two releases are dominated by one decision: all of its gg_*() plotting functions are being moved out into a separate ggtime package. 0.4.2 announced the deprecation and 0.5.0 makes ggtime a dependency with soft-deprecation messages on every re-export.
◆ Where it's heading
The package is narrowing to its stated purpose — features and statistics — and shedding graphics entirely over a deliberately slow two-year window. Everything else in the recent history is ggplot2 compatibility work and narrow seasonal-plot bug fixes, which is consistent with a maintainer trimming surface area rather than growing it.
◆ Prediction
The next releases should be compatibility upkeep while the ggtime deprecation runs its course; the re-exports stay until the announced window closes.
Alternatives to dbparser and feasts
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 dbparser or feasts.
loo
loo keeps rewriting the diagnostics Bayesian modellers read off model comparison
mlr3fselect
mlr3fselect turned feature selection into an asynchronous, distributable job
lime
lime survives on compatibility patches years after its research moment
mlr3measures
mlr3measures is systematically retrofitting sample weights across every metric
mlr3cluster
mlr3cluster went from a handful of clusterers to covering the field
See all dbparser alternatives → · See all feasts alternatives →
Recent activity from dbparser and feasts
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 6mo agofeastsfeasts moves its plots to ggtime behind a 2-year deprecation ⚡
- 11mo agofeastsggplot2 4.0.0 compatibility and the ggtime deprecation notice
- 1y agofeastsgg_season() fix for sub-weekly daily data
- 1y agofeastsImpulse-response plots and Johansen cointegration tests
- 2y agodbparserDuplicate drugbank_id column fixed in drug targets
- 2y agofeastsPatch for ggplot2 3.5.0 breaking changes
- 2y agodbparserTibble column names normalized to snake_case and drugbank_id
- 3y agodbparserPersistence layer dropped; parsers now return a dvobject ⚡
- 3y agofeastsCRAN patch for S3 method consistency
- 5y agodbparserCollective parsers added; parsers reimplemented as R6 classes
- 6y agodbparserMemory and performance gains across parsers
- 6y agodbparserFixes for SQL Server column sizes and dplyr compatibility
Frequently asked questions
What is the difference between dbparser and feasts?
They serve adjacent needs but don't currently overlap on shipped themes. dbparser and feasts 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.
Is dbparser better than feasts?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. dbparser and feasts 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.
What are the best alternatives to dbparser?
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.
What are the best alternatives to feasts?
Top feasts alternatives in Analytics are ranked by recent ship velocity. Browse the "feasts alternatives" section above for the current picks, or visit /alternatives/feasts for the full list with editorial commentary on each.