mlr3proba
mlr3proba is shedding weight as its survival work moves into sibling packages
Comparison · Analytics
Displayr vs patchwork
A side-by-side editorial comparison of Displayr and patchwork — release velocity, themes, recent moves, and the top alternatives to consider.
Displayr vs patchwork: at a glance
What is Displayr?
Chat is being made legible while the survey-analysis core picks up the fundamentals it lacked.
Displayr is shipping on two fronts at a steady, unhurried cadence. The AI assistant is being made auditable rather than more capable — a context pill showing exactly what a prompt will send, a change summary listing every item Chat added, edited or deleted, and an Explain This button that routes errors and warnings into Chat with context attached. Separately the document core is filling in fundamentals: controls that stay synced across pages and page masters, rolling averages computed on date-keyed tables, browser-style back and forward navigation, and templates that can be saved as folder-scoped defaults.
What is patchwork?
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.
Displayr vs patchwork: editorial side-by-side
Displayr
5.0ANALYTICS
Chat is being made legible while the survey-analysis core picks up the fundamentals it lacked.
◆ Current state
Displayr is shipping on two fronts at a steady, unhurried cadence. The AI assistant is being made auditable rather than more capable — a context pill showing exactly what a prompt will send, a change summary listing every item Chat added, edited or deleted, and an Explain This button that routes errors and warnings into Chat with context attached. Separately the document core is filling in fundamentals: controls that stay synced across pages and page masters, rolling averages computed on date-keyed tables, browser-style back and forward navigation, and templates that can be saved as folder-scoped defaults.
◆ Where it's heading
The Chat work reads as a deliberate answer to the trust problem with AI in analyst tools — every release makes what the assistant touched inspectable rather than expanding what it can do unprompted. The other track is closing gaps a long-standing survey analysis platform accumulates, with the default-template mechanic notable for scoping defaults by Cloud Drive folder, which turns a personal preference into an organizational standard. Neither track has produced a directional move in this window.
◆ Prediction
Expect the transparency pattern to extend to Chat actions that modify data rather than layout, since the change summary establishes the mechanism. Folder-scoped defaults look like the start of broader template governance.
patchwork
0.0ANALYTICS
patchwork stopped being a ggplot composer and became a page composer.
◆ Current state
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.
◆ Where it's heading
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.
◆ Prediction
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.
Alternatives to Displayr and patchwork
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 Displayr or patchwork.
mlr3viz
mlr3viz keeps the ecosystem's plots working while the plots themselves move out
mlr3tuning
mlr3tuning is rebuilding its async machinery under a stable public surface
timetk
timetk swallowed anomalize whole, then went quiet for two years
modelbased
modelbased is turning marginal effects into a full contrast grammar
parameters
easystats' parameters package absorbs one more model class every few weeks
See all Displayr alternatives → · See all patchwork alternatives →
Recent activity from Displayr and patchwork
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 22h agoDisplayrUse the Same Control Across Multiple Pages and Page Masters
- 23h agoDisplayrRolling Averages Computed Automatically on Tables
- 16d agoDisplayrExplain This — AI help for errors & warnings
- 16d agoDisplayrBack and Forward Buttons for Navigation
- 16d agoDisplayrSave Templates as Default Visualizations
- 1mo agoDisplayrMore transparency when working with Chat
- 11mo agopatchworkFix spurious load-time warnings
- 1y agopatchworkCompatibility pass for the next ggplot2 release
- 1y agopatchworkgt tables become first-class patchwork objects ⚡
- 2y agopatchworkAxis collection and free() arrive
- 3y agopatchworkPatchworks behave like lists; NULL becomes a no-op
- 3y agopatchworkClearer error when plotting space is too small
Frequently asked questions
What is the difference between Displayr and patchwork?
They serve adjacent needs but don't currently overlap on shipped themes. Displayr is currently shipping more aggressively (velocity 5.0 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 Displayr better than patchwork?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Displayr is currently shipping more aggressively (velocity 5.0 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 Displayr?
Top Displayr alternatives in Analytics are ranked by recent ship velocity. Browse the "Displayr alternatives" section above for the current picks, or visit /alternatives/displayr for the full list with editorial commentary on each.
What are the best alternatives to patchwork?
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.