Omni
Omni ships weekly, and almost every week the headline item is an AI feature.
A side-by-side editorial comparison of ApexCharts and glydraw — release velocity, themes, recent moves, and the top alternatives to consider.
Licensing settled, ApexCharts is back to changing what a chart can take as input.
ApexCharts is deep into a fast v6 line, shipping roughly weekly. The licensing arc that dominated 6.5 through 6.7 — trial watermarks, the first premium-gated chart type, then entitlement checks — has settled, and the last three releases are library work again. 6.9.0 is the largest of them: a histogram type that bins raw samples, a morph engine that conserves marks across chart types, and the end of the library's dependency-free packaging.
SNFG glycan cartoons stopped being pictures and became ggplot2 geoms, guides and axis labels.
glydraw renders glycan structures as SNFG-standard cartoons, standalone or exported in bulk, and since 0.7.0 as native ggplot2 components: geom_glycan() for observations, geom_node_glycan() for ggraph networks, guide_glycan() for legends, and scale_x_glycan() and scale_y_glycan() for discrete axes. Appearance is configured through a single reusable style object rather than scattered arguments, a consolidation that 0.8.0 made breaking. The colour handling now expects a complete SNFG palette rather than sparse per-monosaccharide overrides.
ApexCharts is deep into a fast v6 line, shipping roughly weekly. The licensing arc that dominated 6.5 through 6.7 — trial watermarks, the first premium-gated chart type, then entitlement checks — has settled, and the last three releases are library work again. 6.9.0 is the largest of them: a histogram type that bins raw samples, a morph engine that conserves marks across chart types, and the end of the library's dependency-free packaging.
The through-line now is input and arrangement rather than catalogue size. Charts increasingly accept the measurements a team actually has instead of pre-aggregated values, and the seams that let you hand a chart its own layout — plotOptions.unit.positions, the pluggable layout hook — are being filled in with kits rather than hard-coded options. The premium boundary has stopped moving; the free catalogue keeps growing around it.
Expect the raw-observation pattern to reach another chart type now that the bar pathway handles binning, and expect the remaining pluggable seams to get companion kits the way positions just did.
glydraw renders glycan structures as SNFG-standard cartoons, standalone or exported in bulk, and since 0.7.0 as native ggplot2 components: geom_glycan() for observations, geom_node_glycan() for ggraph networks, guide_glycan() for legends, and scale_x_glycan() and scale_y_glycan() for discrete axes. Appearance is configured through a single reusable style object rather than scattered arguments, a consolidation that 0.8.0 made breaking. The colour handling now expects a complete SNFG palette rather than sparse per-monosaccharide overrides.
The first half of this record is geometry correctness, fixing branch spacing, overlapping linkage annotations, core fucose collisions, triangle alignment and nested side-chain layout, because a cartoon that draws the wrong topology is worse than no cartoon. Once the drawing was trustworthy the package moved outward into ggplot2 and then inward again to consolidate its own API, dropping the glyexp dependency, removing positional argument support, and folding rendering options into style_glydraw(). Each of the last several releases has been explicitly breaking, which is a maintainer using a pre-1.0 window deliberately.
With the style object established and the ggplot2 surface in place, the remaining explicit arguments, show_linkage and orient, are the visible inconsistency and may follow the others into the style. Sibling packages adopt each change within days, as glyenzy did with the new orientation values, so expect the next breaking change to propagate the same way.
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 ApexCharts or glydraw.
Omni ships weekly, and almost every week the headline item is an AI feature.
silx settles into maintenance a release after its PySide6 migration
Plotly is turning its cloud into a metered compute platform with an enterprise on-ramp.
aniread stops asking you to know which tracker wrote the file
Rho's release machinery finally produced a stable build — and it shipped no new product.
Usermaven closed the loop: data comes in from anywhere, and now it goes back out.
See all ApexCharts alternatives → · See all glydraw alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. ApexCharts is currently shipping more aggressively (velocity 10.0 vs 6.3), with 3 editorial sparks in the last 30 days against 1. 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. ApexCharts is currently shipping more aggressively (velocity 10.0 vs 6.3), with 3 editorial sparks in the last 30 days against 1. For your specific use case, the alternatives sections above list other Analytics products to evaluate alongside.
Top ApexCharts alternatives in Analytics are ranked by recent ship velocity. Browse the "ApexCharts alternatives" section above for the current picks, or visit /alternatives/apexcharts for the full list with editorial commentary on each.
Top glydraw alternatives in Analytics are ranked by recent ship velocity. Browse the "glydraw alternatives" section above for the current picks, or visit /alternatives/glydraw for the full list with editorial commentary on each.