ApexCharts
ApexCharts built a paid tier in three releases, then started enforcing it
A side-by-side editorial comparison of dbt Core and billboard.js — release velocity, themes, recent moves, and the top alternatives to consider.
Two engines in one repo: the Python 1.x line tightens while Fusion 2.0 goes lakehouse-catalog native
dbt-core is releasing on two tracks at once. The Python line reached 1.12.0 on 16 July after three release candidates, and it is a tightening release: the experimental `dbt login` command and the bundled dbt-state plugin were removed outright, and flags introduced in 1.9 and 1.10 now default to true. The 2.0.0 alpha track is the Fusion engine, and its work is almost entirely about catalogs — read-write Horizon and Unity access over Iceberg REST via DuckDB, a catalogs.yml v2 covering DuckLake, Iceberg REST and local filesystem, plus catalog_database overrides and Redshift catalog generation through SHOW TABLES and SVV_REDSHIFT_COLUMNS.
billboard.js is adding a canvas renderer — an SVG chart library admitting SVG has a ceiling.
The library is mid-flight on a 4.0.0 pre-release train, and the defining addition is a canvas rendering mode alongside the existing SVG output. The same first candidate made grid, regions and category modules tree-shakable, added file extensions to type declarations, and exported shape option types from the main entry. Everything published since has been canvas follow-up: background image positioning, rendering and touch-interaction parity, candlestick labels aligned to wick endpoints.
dbt-core is releasing on two tracks at once. The Python line reached 1.12.0 on 16 July after three release candidates, and it is a tightening release: the experimental `dbt login` command and the bundled dbt-state plugin were removed outright, and flags introduced in 1.9 and 1.10 now default to true. The 2.0.0 alpha track is the Fusion engine, and its work is almost entirely about catalogs — read-write Horizon and Unity access over Iceberg REST via DuckDB, a catalogs.yml v2 covering DuckLake, Iceberg REST and local filesystem, plus catalog_database overrides and Redshift catalog generation through SHOW TABLES and SVV_REDSHIFT_COLUMNS.
The division of labour between the two tracks is clear from the entries: 1.x is consolidating and removing experiments, while 2.0 is where the new surface area lands. The 2.0 surface is specifically the lakehouse catalog layer — dbt is moving from a tool that writes to a warehouse toward one that binds to open table catalogs directly, with materialization made catalog-aware. Notably 1.12.0rc1 also teaches the Python engine to tolerate Fusion-specific warn_error_options rather than erroring, so the two engines are being made to coexist in the same projects rather than fork.
The alphas are still expanding catalog coverage adapter by adapter, so expect further catalog integrations and continued catalogs.yml v2 work before 2.0 leaves alpha. On the Python side, with the deprecated flags now defaulted and the experimental commands removed, 1.12 looks like a stabilization point rather than a base for new features.
The library is mid-flight on a 4.0.0 pre-release train, and the defining addition is a canvas rendering mode alongside the existing SVG output. The same first candidate made grid, regions and category modules tree-shakable, added file extensions to type declarations, and exported shape option types from the main entry. Everything published since has been canvas follow-up: background image positioning, rendering and touch-interaction parity, candlestick labels aligned to wick endpoints.
Two constraints are being addressed at once. Canvas is the answer to dataset sizes where per-point DOM nodes stop being viable, and the fact that three consecutive candidates are spent on parity fixes shows how much behaviour an SVG-native library has to re-implement to make the alternative renderer feel identical. Tree-shakable modules attack the other constraint — bundle weight — which matters to exactly the same teams choosing a chart library on performance grounds.
Expect further candidates before 4.0.0 stable, still weighted toward canvas parity in interaction and label placement, since that is where every candidate so far has landed.
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 billboard.js.
ApexCharts built a paid tier in three releases, then started enforcing it
Citus keeps three Postgres branches alive while chasing each new major
Three releases in a year, all of them about the Vega dependency — the feed shows nothing else.
Kylin ships once a year with empty release notes and a native engine nobody is being told about.
Iceberg's release cadence is now backports and CVE patches across three live minor lines.
Feature releases every two months in 2024; one bugfix release in the last twelve.
See all dbt Core alternatives → · See all billboard.js alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
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 2 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.
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 2 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.
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.
Top billboard.js alternatives in Analytics are ranked by recent ship velocity. Browse the "billboard.js alternatives" section above for the current picks, or visit /alternatives/billboard-js for the full list with editorial commentary on each.