← Back to home
Comparison · Analytics

bbotk vs dtplyr

A side-by-side editorial comparison of bbotk and dtplyr — release velocity, themes, recent moves, and the top alternatives to consider.

bbotk vs dtplyr: at a glance

Featurebbotkdtplyr
SectorAnalyticsAnalytics
Velocity score2.50.0
Sparks · 30d00
Top themesblack-box optimization, mlr3, async execution, api deprecationdata.table, dplyr, translation, performance
Last editorial update1h ago2h ago
WebsiteVisit →Visit →

What is bbotk?

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.

Read the full bbotk trajectory →

What is dtplyr?

dtplyr stopped hijacking data.table objects and became an opt-in translator

dtplyr converts dplyr and tidyr code into data.table syntax, and 1.3.0 redrew its boundary: verbs no longer dispatch to dtplyr translations just because dtplyr is loaded, so lazy_dt() has to be called explicitly. Since then the work has been translation coverage — reframe(), case_match(), consecutive_id() — plus a long tail of correctness fixes in grouping and .by.

Read the full dtplyr trajectory →

bbotk vs dtplyr: editorial side-by-side

B
bbotk
ANALYTICS
2.5

bbotk is generalizing from an optimizer toolkit into an evaluation framework.

◆ Current state

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.

◆ Where it's heading

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.

◆ Prediction

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.

D
dtplyr
ANALYTICS
0.0

dtplyr stopped hijacking data.table objects and became an opt-in translator

◆ Current state

dtplyr converts dplyr and tidyr code into data.table syntax, and 1.3.0 redrew its boundary: verbs no longer dispatch to dtplyr translations just because dtplyr is loaded, so lazy_dt() has to be called explicitly. Since then the work has been translation coverage — reframe(), case_match(), consecutive_id() — plus a long tail of correctness fixes in grouping and .by.

◆ Where it's heading

The package is trailing dplyr's own feature releases rather than leading them, adding each new verb once it settles upstream. Performance work is targeted at specific verbs where data.table has a faster primitive: setorder() for arrange(), reference drops for select(), rleid() for consecutive_id(). Release cadence has thinned considerably since 2023.

◆ Prediction

Expect further one-for-one translations as dplyr adds verbs, and continued fixes around .by and non-standard column names; the entries show no sign of a broader redesign.

Alternatives to bbotk and dtplyr

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 dtplyr.

See all bbotk alternatives → · See all dtplyr alternatives →

Recent activity from bbotk and dtplyr

Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.

  1. 24d agobbotkDeprecated extra argument removed from ArchiveAsync methods
  2. 1mo agobbotkArchiveAsync gains full push/finish/fail task API over rush
  3. 2mo agobbotkDominance and hypervolume computation moved to moocore
  4. 4mo agobbotkmlr_test_functions adds standard optimization benchmarks
  5. 5mo agobbotkEvalInstance base class separates evaluation from optimization
  6. 8mo agobbotkFix: conditions now work with OptimizerLocalSearch
  7. 11mo agodtplyrreframe(), case_match() and consecutive_id() gain translations
  8. 3y agodtplyrcrayon dependency dropped
  9. 3y agodtplyrVerbs stop auto-dispatching; lazy_dt() now required
  10. 3y agodtplyrdtplyr 1.2.2
  11. 4y agodtplyrdtplyr 1.2.1
  12. 4y agodtplyrEight tidyr verbs gain data.table translations

Frequently asked questions

What is the difference between bbotk and dtplyr?

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.

Is bbotk better than dtplyr?

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.

What are the best alternatives to bbotk?

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.

What are the best alternatives to dtplyr?

Top dtplyr alternatives in Analytics are ranked by recent ship velocity. Browse the "dtplyr alternatives" section above for the current picks, or visit /alternatives/dtplyr for the full list with editorial commentary on each.