mlr3proba
mlr3proba is shedding weight as its survival work moves into sibling packages
Comparison · Analytics
dbt Core vs patchwork
A side-by-side editorial comparison of dbt Core and patchwork — release velocity, themes, recent moves, and the top alternatives to consider.
dbt Core vs patchwork: at a glance
What is dbt Core?
dbt keeps three maintenance branches alive while Fusion 2.0 crosses into beta.
dbt-core is running two lines at once: a Python 1.x maintenance train across 1.10, 1.11 and 1.12, and the Rust Fusion 2.0 rewrite now in its first beta. The August 12 batch pushed the same deprecated-version warning into all three maintenance branches on one day, with the substantive work isolated to 1.12.1 (OpenTelemetry spans for node and hook execution) and 1.11.13 (deterministic unit-test resolution). Fusion is where the capability surface is actually widening.
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.
dbt Core vs patchwork: editorial side-by-side
dbt Core
7.5ANALYTICS
dbt keeps three maintenance branches alive while Fusion 2.0 crosses into beta.
◆ Current state
dbt-core is running two lines at once: a Python 1.x maintenance train across 1.10, 1.11 and 1.12, and the Rust Fusion 2.0 rewrite now in its first beta. The August 12 batch pushed the same deprecated-version warning into all three maintenance branches on one day, with the substantive work isolated to 1.12.1 (OpenTelemetry spans for node and hook execution) and 1.11.13 (deterministic unit-test resolution). Fusion is where the capability surface is actually widening.
◆ Where it's heading
The 1.x branches are converging on housekeeping — deprecation warnings, jsonschema definitions synced down from Fusion, parse-order determinism, adapter config recognition. That is the signature of a codebase being held stable rather than extended. Fusion 2.0 is absorbing the new work: catalog-free binding, a lint rule engine, node selection for lint and format, a self-hostable docs server.
◆ Prediction
Expect the maintenance branches to keep taking cross-branch warnings and adapter-config fixes while Fusion moves through further betas. The OpenTelemetry work in 1.12.1 is flag-gated behind --snowflake-projects-otel, which suggests tracing arrives unflagged in a later release.
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 dbt Core 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 dbt Core 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 dbt Core alternatives → · See all patchwork alternatives →
Recent activity from dbt Core and patchwork
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 23h agodbt Coredbt 1.12.2 stops flagging Databricks configs as unknown keys
- 1d agodbt Coredbt 1.10.23 backports the deprecated-version warning
- 1d agodbt Coredbt 1.11.13 makes unit-test model resolution parse-order independent
- 1d agodbt Coredbt 1.12.1 adds OpenTelemetry spans for node and hook execution
- 3d agodbt Coredbt Fusion 2.0 reaches its first beta with catalog-free SQL binding ⚡
- 24d agodbt CoreFusion alpha.5 adds catalog_database and Redshift datasharing catalogs
- 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 dbt Core and patchwork?
They serve adjacent needs but don't currently overlap on shipped themes. dbt Core is currently shipping more aggressively (velocity 7.5 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 dbt Core better than patchwork?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. dbt Core is currently shipping more aggressively (velocity 7.5 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 dbt Core?
Top dbt Core alternatives in Analytics are ranked by recent ship velocity. Browse the "dbt Core alternatives" section above for the current picks, or visit /alternatives/dbt-core 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.