rnaturalearth
rnaturalearth finished its sp exit and is now optimising how the data actually arrives.
Comparison · Analytics
mlr3tuning vs taxa
A side-by-side editorial comparison of mlr3tuning and taxa — release velocity, themes, recent moves, and the top alternatives to consider.
mlr3tuning vs taxa: at a glance
What is mlr3tuning?
mlr3tuning is rebuilding its async machinery under a stable public surface
mlr3tuning provides hyperparameter optimization for the mlr3 ecosystem, and its recent history is dominated by the asynchronous tuning path: archive freezing, callback stages around queue evaluation, and version-locked compatibility with the rush backend. Releases pair a small feature with several fixes and an explicit compatibility line naming the mlr3 or rush version they track. The most recent release drops all workarounds for older rush versions, which suggests that dependency has stabilized enough to require rather than accommodate.
What is taxa?
taxa started a ground-up rewrite in 2021 and has published almost nothing since.
0.4.0 began a complete rewrite aimed at making the component classes behave like base R vectors, explicitly shipping without the `taxmap` class and parking the old implementation inside metacoder until the new one matured. Four years later that is still where things stand: 0.4.2 experimented with `''` instead of `NA` for missing values and chased a vctrs test break, and 0.4.4 fixed CRAN check issues. The releases before the rewrite were the productive ones — `taxonomy_table()`, `print_tree()`, `get_dataset()`, fuzzy name matching, faster parsers.
mlr3tuning vs taxa: editorial side-by-side
mlr3tuning
2.5ANALYTICS
mlr3tuning is rebuilding its async machinery under a stable public surface
◆ Current state
mlr3tuning provides hyperparameter optimization for the mlr3 ecosystem, and its recent history is dominated by the asynchronous tuning path: archive freezing, callback stages around queue evaluation, and version-locked compatibility with the rush backend. Releases pair a small feature with several fixes and an explicit compatibility line naming the mlr3 or rush version they track. The most recent release drops all workarounds for older rush versions, which suggests that dependency has stabilized enough to require rather than accommodate.
◆ Where it's heading
Two things are being tidied at once. The async archive is converging on a consistent data.table representation across batch and async variants, so results are shaped the same regardless of how tuning ran. Separately, the package is becoming a better ecosystem citizen — unioning tuner properties on load instead of overwriting them, removing its callbacks on unload, and raising informative errors from AutoTuner accessors on an untrained model. Both are the marks of a package used as a dependency more than as a destination.
◆ Prediction
With rush pinned to 1.2.0 and the compatibility shims gone, the next release is likely to expose more of the async path through callbacks rather than change the tuning interface.
taxa
0.0ANALYTICS
taxa started a ground-up rewrite in 2021 and has published almost nothing since.
◆ Current state
0.4.0 began a complete rewrite aimed at making the component classes behave like base R vectors, explicitly shipping without the `taxmap` class and parking the old implementation inside metacoder until the new one matured. Four years later that is still where things stand: 0.4.2 experimented with `''` instead of `NA` for missing values and chased a vctrs test break, and 0.4.4 fixed CRAN check issues. The releases before the rewrite were the productive ones — `taxonomy_table()`, `print_tree()`, `get_dataset()`, fuzzy name matching, faster parsers.
◆ Where it's heading
The rewrite has not landed. `taxmap`, the class most users came for, was never reimplemented in the new design, and the only releases since are CRAN compliance. Meanwhile metacoder still carries the old taxa, which means the ecosystem is running on the version the rewrite was meant to replace. This reads as a stalled migration rather than an active one.
◆ Prediction
Nothing in the entries indicates the rewrite is resuming; the likely next release is another CRAN-check fix. Whether `taxmap` ever arrives in the new design is unresolved.
Alternatives to mlr3tuning and taxa
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 mlr3tuning or taxa.
writexl
writexl spent nine years refusing to do formatting, then shipped all of it in 2.0.0.
rgbif
rgbif is steadily pushing users off paged searching and onto real downloads.
rstanarm
rstanarm is community-maintained now, tracking Stan and lme4 rather than adding models.
rotl
rotl's whole release history is keeping name matching honest against a moving taxonomy.
taxize
taxize spends its releases absorbing other people's API changes, one dead source at a time.
See all mlr3tuning alternatives → · See all taxa alternatives →
Recent activity from mlr3tuning and taxa
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 18d agomlr3tuningmlr3tuning 1.6.1 stops clobbering other packages' tuner properties
- 4mo agomlr3tuningmlr3tuning 1.6.0 aligns archive column order across tuning classes
- 8mo agomlr3tuningmlr3tuning 1.5.1 tracks xgboost 3.1.2.1
- 8mo agomlr3tuningmlr3tuning 1.5.0 adds queue evaluation stages to async callbacks
- 1y agotaxataxa 0.4.4 fixes CRAN check issues
- 1y agomlr3tuningmlr3tuning 1.4.0 unifies logging under a base mlr3 logger
- 1y agomlr3tuningmlr3tuning 1.3.0 adds a frozen async archive and leaner worker storage
- 4y agotaxataxa 0.4.2 tries empty strings for missing values
- 5y agotaxataxa 0.4.0 begins a base-R-vector rewrite without taxmap ⚡
- 6y agotaxataxa 0.3.4 fixes n_obs with numeric column names
- 6y agotaxataxa 0.3.3 supports numeric column names in taxmap
- 7y agotaxataxa 0.3.2 fixes parsers and adds negative class_col indexes
Frequently asked questions
What is the difference between mlr3tuning and taxa?
They serve adjacent needs but don't currently overlap on shipped themes. mlr3tuning 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 mlr3tuning better than taxa?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. mlr3tuning 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 mlr3tuning?
Top mlr3tuning alternatives in Analytics are ranked by recent ship velocity. Browse the "mlr3tuning alternatives" section above for the current picks, or visit /alternatives/mlr3tuning for the full list with editorial commentary on each.
What are the best alternatives to taxa?
Top taxa alternatives in Analytics are ranked by recent ship velocity. Browse the "taxa alternatives" section above for the current picks, or visit /alternatives/taxa-r for the full list with editorial commentary on each.