rnaturalearth
rnaturalearth finished its sp exit and is now optimising how the data actually arrives.
A side-by-side editorial comparison of bbotk and writexl — 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.
writexl spent nine years refusing to do formatting, then shipped all of it in 2.0.0.
For most of its history writexl was a deliberately minimal wrapper: bump the vendored libxlsxwriter, handle NA and Date coercion correctly, support a list of data frames for multiple sheets, and nothing else. 2.0.0, released August 2026, changes that — near-full libxlsxwriter coverage, cell/worksheet/workbook formatting, cell comments, an `xl_cell_general` class carrying value, formula and hyperlink, a cell-by-cell refactor, libxlsxwriter 1.2.4, and memory-safety work. It landed the same day as 1.5.4, a typo fix on the old line.
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.
For most of its history writexl was a deliberately minimal wrapper: bump the vendored libxlsxwriter, handle NA and Date coercion correctly, support a list of data frames for multiple sheets, and nothing else. 2.0.0, released August 2026, changes that — near-full libxlsxwriter coverage, cell/worksheet/workbook formatting, cell comments, an `xl_cell_general` class carrying value, formula and hyperlink, a cell-by-cell refactor, libxlsxwriter 1.2.4, and memory-safety work. It landed the same day as 1.5.4, a typo fix on the old line.
The package has changed category. Its selling point was being the dependency-free, opinion-free way to get a data frame into xlsx; 2.0.0 makes it a formatting-capable writer that now compares itself against openxlsx2 in its own test suite. The cell-by-cell refactor is what made that possible and is also the largest structural change in the package's history. Note that a single contributor drove essentially all of it.
Expect follow-up releases fixing edge cases in the new formatting and comment APIs — the cell-by-cell rewrite is too large to land clean, and the 2.0.0 notes already mention an off-by-one in date columns.
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 writexl.
rnaturalearth finished its sp exit and is now optimising how the data actually arrives.
rgbif is steadily pushing users off paged searching and onto real downloads.
rstanarm is community-maintained now, tracking Stan and lme4 rather than adding models.
taxa started a ground-up rewrite in 2021 and has published almost nothing since.
rotl's whole release history is keeping name matching honest against a moving taxonomy.
taxize spends its releases absorbing other people's API changes, one dead source at a time.
See all bbotk alternatives → · See all writexl alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. writexl is currently shipping more aggressively (velocity 6.3 vs 2.5), with 1 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. writexl is currently shipping more aggressively (velocity 6.3 vs 2.5), with 1 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 writexl alternatives in Analytics are ranked by recent ship velocity. Browse the "writexl alternatives" section above for the current picks, or visit /alternatives/writexl for the full list with editorial commentary on each.