RMVMR
RMVMR is being tidied in lockstep with MVMR, the package it wraps
Comparison · Analytics
dbt Core vs units
A side-by-side editorial comparison of dbt Core and units — release velocity, themes, recent moves, and the top alternatives to consider.
dbt Core vs units: at a glance
What is dbt Core?
dbt-core spent a day backporting one deprecation warning across eight EOL branches — the message is: upgrade.
dbt-core maintains an unusually wide set of live branches, and on August 14 it cut releases for 1.1 through 1.8 in a single day. Every one of them carries the same single feature: a warning when the user is running a deprecated dbt version. The older branches picked up a few long-standing backports alongside it — semver comparison, JSON log formatting, seeds from stored manifest data — and 1.4 through 1.6 dropped Python 3.8 testing now that it is end of life.
What is units?
units reaches 1.0 by rewriting its parser and accepting the breakage that comes with it.
units attaches physical units to R vectors on top of the udunits2 library, covering arithmetic, conversion and ggplot2 scales. Version 1.0-0 replaced the unit-expression tokenizer so numbers are consistently treated as prefixes, and expressions like ml/min/1.73m^2 now parse the way physiologists write them. Printing follows NIST conventions, and 1.0-1 is a fix pass over memory handling and parser edge cases.
dbt Core vs units: editorial side-by-side
dbt Core
7.5ANALYTICS
dbt-core spent a day backporting one deprecation warning across eight EOL branches — the message is: upgrade.
◆ Current state
dbt-core maintains an unusually wide set of live branches, and on August 14 it cut releases for 1.1 through 1.8 in a single day. Every one of them carries the same single feature: a warning when the user is running a deprecated dbt version. The older branches picked up a few long-standing backports alongside it — semver comparison, JSON log formatting, seeds from stored manifest data — and 1.4 through 1.6 dropped Python 3.8 testing now that it is end of life.
◆ Where it's heading
This is a coordinated deprecation campaign rather than product work. Shipping the same warning to every ancient branch at once is how a maintainer starts reclaiming a support surface, and the parallel removal of Python 3.8 support points the same way. The actual development is happening on 1.11 and 1.12, where recent releases sync JSON schemas from dbt-fusion and fix adapter config recognition — the branch where the Fusion engine transition is visible.
◆ Prediction
Expect formal end-of-life announcements for the branches that just received the warning, and continued dbt-fusion schema convergence on 1.12. The backport waves should thin out once the deprecated branches are formally retired.
units
0.0ANALYTICS
units reaches 1.0 by rewriting its parser and accepting the breakage that comes with it.
◆ Current state
units attaches physical units to R vectors on top of the udunits2 library, covering arithmetic, conversion and ggplot2 scales. Version 1.0-0 replaced the unit-expression tokenizer so numbers are consistently treated as prefixes, and expressions like ml/min/1.73m^2 now parse the way physiologists write them. Printing follows NIST conventions, and 1.0-1 is a fix pass over memory handling and parser edge cases.
◆ Where it's heading
The long 0.8-x run was accretion — ggplot2 scales absorbed from ggforce, ud_convert(), matrix methods, steady performance work — while known parsing defects stayed in place. The 1.0 release finally traded backwards compatibility for correct parsing, and 1.0-1's pointer-wrapping and exception-propagation work suggests the C++ glue is being hardened behind it. Fixes cluster at the udunits2 boundary, which remains the main source of surprises.
◆ Prediction
Expect continued patch releases against udunits2 quirks and the new tokenizer's fallout rather than new surface area, with the ggplot2 integration and conversion helpers already in place.
Alternatives to dbt Core and units
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 units.
geoarrow-r
geoarrow tracks the GeoArrow spec and otherwise just keeps compiling
n2khab
n2khab keeps retracting interpretations of habitat data it can't actually support
tidypolars
tidypolars is grinding toward complete dplyr coverage, one supported function at a time
OneSampleMR
OneSampleMR found that argument order in a formula was silently changing its estimates
bpbounds
bpbounds found the same swapped-cell bug twice and clamped its bounds back into range
See all dbt Core alternatives → · See all units alternatives →
Recent activity from dbt Core and units
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 1d agodbt Coredbt 1.2.7 backports the deprecated-version warning and old fixes
- 1d agodbt Coredbt 1.1.6 backports the deprecated-version warning and old fixes
- 1d agodbt Coredbt 1.3.8 backports the deprecated-version warning
- 1d agodbt Coredbt 1.4.10 drops Python 3.8 and warns on deprecated versions
- 1d agodbt Coredbt 1.5.12 drops Python 3.8 and warns on deprecated versions
- 1d agodbt Coredbt 1.6.19 drops Python 3.8 and warns on deprecated versions
- 5mo agounitsMemory-leak and udunits2 parsing fixes after 1.0
- 10mo agounitsNew tokenizer parses compound units correctly ⚡
- 1y agounitsCopy semantics fix in ud_convert(); C++17 for old R
- 1y agounitscbind/rbind methods, ud_convert() and broad fixes
- 1y agounitsSilences a CRAN compiler warning
- 2y agounitsRestores simplify=FALSE for identical units
Frequently asked questions
What is the difference between dbt Core and units?
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 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 dbt Core better than units?
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 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 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 units?
Top units alternatives in Analytics are ranked by recent ship velocity. Browse the "units alternatives" section above for the current picks, or visit /alternatives/units-r for the full list with editorial commentary on each.