← Back to home
Comparison · Analytics

stacks vs writexl

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

stacks vs writexl: at a glance

Featurestackswritexl
SectorAnalyticsAnalytics
Velocity score0.06.3
Sparks · 30d01
Top themestidymodels, ensembling, parallel-processing, future-frameworkxlsx, libxlsxwriter, cell-formatting, major-version
Last editorial update1h ago51m ago
WebsiteVisit →Visit →

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.

Read the full stacks trajectory →

What is writexl?

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.

Read the full writexl trajectory →

stacks vs writexl: editorial side-by-side

S
stacks
ANALYTICS
0.0

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.

W
writexl
ANALYTICS
6.3

writexl spent nine years refusing to do formatting, then shipped all of it in 2.0.0.

◆ Current state

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.

◆ Where it's heading

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.

◆ Prediction

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.

Alternatives to stacks and writexl

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

See all stacks alternatives → · See all writexl alternatives →

Recent activity from stacks and writexl

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

  1. 8d agowritexlwritexl 2.0.0 adds formatting, comments and full libxlsxwriter coverage
  2. 8d agowritexlwritexl 1.5.4 fixes a documentation typo
  3. 1y agostacksstacks 1.1.1 re-released to clear a CRAN check note
  4. 1y agostacksstacks 1.1.0 completes the move to future-based parallelism
  5. 2y agostacksstacks 1.0.5 fixes butchered stack size inflation
  6. 2y agostacksstacks 1.0.4 introduces future-based parallel processing
  7. 2y agostacksstacks 1.0.3 clears recipes deprecations and a type-check bug
  8. 3y agostacksstacks 1.0.2 adds an augment() method for vetiver compatibility
  9. 5y agowritexlwritexl 1.4.0 updates libxlsxwriter to 1.0.3
  10. 6y agowritexlwritexl 1.2 fixes NA in formulas and hyperlinks
  11. 7y agowritexlwritexl 1.1 fixes NA strings and bit64 coercion
  12. 8y agowritexlwritexl 1.0 writes Date values as datetimes

Frequently asked questions

What is the difference between stacks and writexl?

They serve adjacent needs but don't currently overlap on shipped themes. writexl is currently shipping more aggressively (velocity 6.3 vs 0.0), 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.

Is stacks better than writexl?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. writexl is currently shipping more aggressively (velocity 6.3 vs 0.0), 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.

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 writexl?

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.