tidytext
Finished, widely taught, and shipping roxygen fixes.
A side-by-side editorial comparison of fable and patchwork — release velocity, themes, recent moves, and the top alternatives to consider.
fable keeps widening its model shelf, one econometric class at a time
fable is the tidyverts forecasting engine, and its releases are almost entirely about which model families it can express. The 0.4.x line added the vector-error-correction and VARIMA classes plus impulse-response methods; 0.5.0 adds fractional differencing via ARFIMA. Between those, the releases are CRAN-check patches and documentation passes.
patchwork stopped being a ggplot composer and became a page composer.
patchwork assembles plots into compositions with arithmetic operators, and the 1.x line has steadily hardened that grammar: guide and axis collection, free() to exempt a plot from alignment, inset_element() for overlays, and list-like behaviour so lapply() and length() work on a patchwork. Version 1.3.0 added native gt table support. The two releases since are a load-time warning fix and a compatibility pass for the next ggplot2 release.
fable is the tidyverts forecasting engine, and its releases are almost entirely about which model families it can express. The 0.4.x line added the vector-error-correction and VARIMA classes plus impulse-response methods; 0.5.0 adds fractional differencing via ARFIMA. Between those, the releases are CRAN-check patches and documentation passes.
The package is closing the gap with the older forecast package's model coverage while keeping the tidy model-specification grammar. Each substantive release is a new model class plus the generate()/IRF() plumbing to make it behave like the existing ones. Maintenance releases cluster around CRAN policy and ggplot2/tsibble compatibility rather than internal rewrites.
Expect the next substantive release to add another model class or extend generate()/IRF() coverage to the classes that still lack them, rather than change the modelling interface.
patchwork assembles plots into compositions with arithmetic operators, and the 1.x line has steadily hardened that grammar: guide and axis collection, free() to exempt a plot from alignment, inset_element() for overlays, and list-like behaviour so lapply() and length() work on a patchwork. Version 1.3.0 added native gt table support. The two releases since are a load-time warning fix and a compatibility pass for the next ggplot2 release.
The centre of gravity is shifting from alignment mechanics to composition scope. Early releases were almost entirely bug fixes against grid and ggplot2 internals — strip placement, fixed aspect ratios, guide merging. Recent ones add object types and escape hatches instead. Between feature cycles the package is in maintenance defined by ggplot2's release calendar, which is what 1.3.1 is in its entirety.
Expect wrap_table() to grow beyond gt to other table objects, and expect the next substantive release to be triggered by a ggplot2 internals change rather than by a patchwork roadmap.
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 fable or patchwork.
Finished, widely taught, and shipping roxygen fixes.
Text features finally stay sparse all the way to the model.
The package that made calibration a step instead of an afterthought.
workflowsets keeps widening what counts as a model worth comparing.
The tidymodels pipeline grew a third stage, and it happens after the model runs.
Posit's MLOps package went quiet for two years, then came back to keep up with recipes.
See all fable alternatives → · See all patchwork alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. fable and patchwork 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.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. fable and patchwork 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.
Top fable alternatives in Analytics are ranked by recent ship velocity. Browse the "fable alternatives" section above for the current picks, or visit /alternatives/fable for the full list with editorial commentary on each.
Top patchwork alternatives in Analytics are ranked by recent ship velocity. Browse the "patchwork alternatives" section above for the current picks, or visit /alternatives/patchwork for the full list with editorial commentary on each.