tidytext
Finished, widely taught, and shipping roxygen fixes.
Comparison · Analytics
dbparser vs loo
A side-by-side editorial comparison of dbparser and loo — release velocity, themes, recent moves, and the top alternatives to consider.
dbparser vs loo: 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 loo?
loo keeps rewriting the diagnostics Bayesian modellers read off model comparison
loo computes leave-one-out cross-validation and model comparison for Bayesian models in the Stan ecosystem. Two releases in this window changed what users actually read: 2.7.0 replaced the fixed Pareto-k thresholds with sample-size-dependent ones and dropped the middle category, and 2.10.0 reshaped loo_compare's output into a data.frame with new uncertainty columns. The releases between are diagnostic robustness fixes and moment-matching corrections.
dbparser vs loo: 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.
loo
2.5ANALYTICS
loo keeps rewriting the diagnostics Bayesian modellers read off model comparison
◆ Current state
loo computes leave-one-out cross-validation and model comparison for Bayesian models in the Stan ecosystem. Two releases in this window changed what users actually read: 2.7.0 replaced the fixed Pareto-k thresholds with sample-size-dependent ones and dropped the middle category, and 2.10.0 reshaped loo_compare's output into a data.frame with new uncertainty columns. The releases between are diagnostic robustness fixes and moment-matching corrections.
◆ Where it's heading
The package is being brought in line with the current PSIS literature rather than extended with new features, and the practical effect is that the numbers practitioners quote in papers keep changing meaning. Work is increasingly delegated to posterior for shared computations, and the project has added contributor process, benchmarks and a published AI contribution policy.
◆ Prediction
Expect further work on comparison diagnostics — the p_worse and diag_* columns are new enough that their defaults and documentation will likely be revised next.
Alternatives to dbparser and loo
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 loo.
textrecipes
Text features finally stay sparse all the way to the model.
probably
The package that made calibration a step instead of an afterthought.
workflowsets
workflowsets keeps widening what counts as a model worth comparing.
workflows
The tidymodels pipeline grew a third stage, and it happens after the model runs.
vetiver
Posit's MLOps package went quiet for two years, then came back to keep up with recipes.
See all dbparser alternatives → · See all loo alternatives →
Recent activity from dbparser and loo
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 20d agoloopsis_smooth_tail revert and simplify arg restored
- 1mo agolooloo_compare returns a data.frame with new uncertainty columns ⚡
- 7mo agolooStacking overflow fixes and posterior-based ESS
- 2y agolooMore robust Pareto-k diagnostics and moment matching
- 2y agodbparserDuplicate drugbank_id column fixed in drug targets
- 2y agolooPareto-k thresholds now depend on sample size ⚡
- 2y agodbparserTibble column names normalized to snake_case and drugbank_id
- 3y agodbparserPersistence layer dropped; parsers now return a dvobject ⚡
- 3y agolooLOO predictive metrics and CRPS scoring functions
- 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 loo?
They serve adjacent needs but don't currently overlap on shipped themes. loo 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.
Is dbparser better than loo?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. loo 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.
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 loo?
Top loo alternatives in Analytics are ranked by recent ship velocity. Browse the "loo alternatives" section above for the current picks, or visit /alternatives/loo for the full list with editorial commentary on each.