rnaturalearth
rnaturalearth finished its sp exit and is now optimising how the data actually arrives.
Comparison · Analytics
stacks vs taxize
A side-by-side editorial comparison of stacks and taxize — release velocity, themes, recent moves, and the top alternatives to consider.
stacks vs taxize: at a glance
What is stacks?
Model stacking in tidymodels, quietly migrating off foreach and onto future
stacks builds ensembles from tidymodels tuning results, and its release history is dominated by one long project: replacing foreach-based parallelism with the future framework. That transition completed in 1.1.0, where foreach backends began being ignored with a warning and the minimum R version rose to 4.1. Releases are infrequent and small, with the most recent being a CRAN re-submission rather than a change.
What is taxize?
taxize spends its releases absorbing other people's API changes, one dead source at a time.
The most recent work is migration: 0.10.0 replaced the deprecated Global Names Resolver functions with GNA equivalents (`gna_verifier`, `gna_parse`), rewrote `scrapenames` for the new API, and updated its rredlist usage to match that package's own v4 rewrite. 0.10.1 then tuned `gna_verifier`'s batch size to 50. The older entries in the window show the same shape from a different angle: `tnrs()` made defunct because the service died, COL dropped over rate limiting, NatureServe reworked for a new API, and a package-wide parameter rename to `sci` / `com` / `id` / `sci_com` / `sci_id`.
stacks vs taxize: editorial side-by-side
stacks
0.0ANALYTICS
Model stacking in tidymodels, quietly migrating off foreach and onto future
◆ Current state
stacks builds ensembles from tidymodels tuning results, and its release history is dominated by one long project: replacing foreach-based parallelism with the future framework. That transition completed in 1.1.0, where foreach backends began being ignored with a warning and the minimum R version rose to 4.1. Releases are infrequent and small, with the most recent being a CRAN re-submission rather than a change.
◆ Where it's heading
The package is mature and its remaining work is compatibility rather than capability — tracking the parallelism story across tidymodels, keeping object sizes sane after butchering and reloading, and staying aligned with recipes deprecations. The augment() method added for vetiver compatibility shows the same instinct: fit into the surrounding ecosystem rather than grow independently of it. Nothing in the visible history suggests new ensembling methods are being pursued.
◆ Prediction
With the future migration finished, the next release is most likely maintenance keeping pace with tune and recipes rather than anything users would notice.
taxize
0.0ANALYTICS
taxize spends its releases absorbing other people's API changes, one dead source at a time.
◆ Current state
The most recent work is migration: 0.10.0 replaced the deprecated Global Names Resolver functions with GNA equivalents (`gna_verifier`, `gna_parse`), rewrote `scrapenames` for the new API, and updated its rredlist usage to match that package's own v4 rewrite. 0.10.1 then tuned `gna_verifier`'s batch size to 50. The older entries in the window show the same shape from a different angle: `tnrs()` made defunct because the service died, COL dropped over rate limiting, NatureServe reworked for a new API, and a package-wide parameter rename to `sci` / `com` / `id` / `sci_com` / `sci_id`.
◆ Where it's heading
taxize's job is aggregating a dozen taxonomic databases, so most of its engineering is downstream of decisions it does not control — sources go away, endpoints change, rate limits appear. The visible trend is consolidation: fewer, better-maintained backends rather than broader coverage. Release cadence has thinned to roughly one a year, and the rredlist coupling means it now inherits that package's breaking changes too.
◆ Prediction
Expect the next release to track another upstream source change rather than add new databases; the deprecated-parameter aliases from the 0.9.97 rename are also overdue for removal.
Alternatives to stacks and taxize
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 stacks or taxize.
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.
taxa
taxa started a ground-up rewrite in 2021 and has published almost nothing since.
rotl
rotl's whole release history is keeping name matching honest against a moving taxonomy.
See all stacks alternatives → · See all taxize alternatives →
Recent activity from stacks and taxize
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 5mo agotaxizetaxize 0.10.1 lowers gna_verifier batch size
- 1y agostacksstacks 1.1.1 re-released to clear a CRAN check note
- 1y agostacksstacks 1.1.0 completes the move to future-based parallelism
- 1y agotaxizetaxize 0.10.0 migrates to GNA and the new rredlist API
- 2y agostacksstacks 1.0.5 fixes butchered stack size inflation
- 2y agostacksstacks 1.0.4 introduces future-based parallel processing
- 2y agostacksstacks 1.0.3 clears recipes deprecations and a type-check bug
- 3y agostacksstacks 1.0.2 adds an augment() method for vetiver compatibility
- 5y agotaxizetaxize 0.9.99 retires tnrs(), paginates WORMS queries
- 5y agotaxizetaxize 0.9.98 adds NCBI and zoological rank names
- 6y agotaxizetaxize 0.9.97 standardises parameter names package-wide
- 6y agotaxizetaxize 0.9.96 updates NatureServe for its new API
Frequently asked questions
What is the difference between stacks and taxize?
They serve adjacent needs but don't currently overlap on shipped themes. stacks and taxize 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 stacks better than taxize?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. stacks and taxize 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 stacks?
Top stacks alternatives in Analytics are ranked by recent ship velocity. Browse the "stacks alternatives" section above for the current picks, or visit /alternatives/stacks for the full list with editorial commentary on each.
What are the best alternatives to taxize?
Top taxize alternatives in Analytics are ranked by recent ship velocity. Browse the "taxize alternatives" section above for the current picks, or visit /alternatives/taxize for the full list with editorial commentary on each.