Chord
Chord's assistant can now write to the team's knowledge base, not just read from it.
A side-by-side editorial comparison of bittermelon and vellum — release velocity, themes, recent moves, and the top alternatives to consider.
bittermelon is growing from binary bitmaps toward greyscale and color glyphs
The package manipulates bitmap fonts and bitmaps in R, and the recent direction is widening what a glyph can be. v2.3.1 adds greyscale font support by reading the experimental yaff levels property into pixmap glyphs with alpha derived from the level fraction, and makes writing a multi-colored glyph an error rather than silently clamping it. Earlier releases built out the same surface: bm_extract(), an interactive pixel picker, data frame coercion, and format support for other packages' bitmap types.
vellum's bugs are now found by using it, not testing it — the downstream grammar is doing the QA.
The rendering engine shipped nine releases in the two weeks around the end of July, six of them on a single day. Almost every entry is a correctness fix in a capability that worked when drawn and failed when measured, or worked in isolation and failed in composition. The release notes are unusually forensic: each one states the mechanism, the observable symptom, and why the fix mirrors the draw path rather than reimplementing it.
The package manipulates bitmap fonts and bitmaps in R, and the recent direction is widening what a glyph can be. v2.3.1 adds greyscale font support by reading the experimental yaff levels property into pixmap glyphs with alpha derived from the level fraction, and makes writing a multi-colored glyph an error rather than silently clamping it. Earlier releases built out the same surface: bm_extract(), an interactive pixel picker, data frame coercion, and format support for other packages' bitmap types.
Two things are converging. The representation is moving beyond one-bit glyphs — pixmaps, color, and now greyscale levels with transparency — while the API gets stricter about the boundary between them, refusing to quietly downcast a color glyph on write. Separately, the package has been shedding weight: the embedded monobit copy was removed once it outgrew CRAN size limits, pushing format breadth onto a user-installed dependency.
Expect further greyscale and color work now that levels parsing exists — most likely writing that format rather than only reading it, since the write path is where the current release chose to draw a hard error instead.
The rendering engine shipped nine releases in the two weeks around the end of July, six of them on a single day. Almost every entry is a correctness fix in a capability that worked when drawn and failed when measured, or worked in isolation and failed in composition. The release notes are unusually forensic: each one states the mechanism, the observable symptom, and why the fix mirrors the draw path rather than reimplementing it.
The pivotal detail is stated outright in 0.6.3 — the first bug in the series found by using the engine from vellumplot rather than testing it in isolation. Every release since names the downstream as the source: the contrast rule's false positives, the lint rules that fired on all five sample plots, the keyed roundrect batch. A rendering engine with a real grammar built on top of it is now getting the integration coverage that unit tests structurally cannot provide, and the fixes are converging on one theme: the measurement path and the draw path must not drift.
Expect the release rate to fall as the vellumplot integration surface is exhausted, with remaining work concentrated in the lint rule set now that it is meant to gate builds rather than just inform.
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 bittermelon or vellum.
Chord's assistant can now write to the team's knowledge base, not just read from it.
tidytransit tracks the GTFS spec as it grows, one reader and one router feature at a time.
A tiny grid renderer for oblique-projection cubes, complete since its first release.
BioCro swapped an unstable iteration for real root finders, changing what its crop models compute.
redist keeps rewriting the sampler underneath a district-drawing API it has held stable since 4.0.
epiflows has shipped four releases in eight years, none of which changed the code.
See all bittermelon alternatives → · See all vellum alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. vellum 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.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. vellum 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.
Top bittermelon alternatives in Analytics are ranked by recent ship velocity. Browse the "bittermelon alternatives" section above for the current picks, or visit /alternatives/bittermelon-r for the full list with editorial commentary on each.
Top vellum alternatives in Analytics are ranked by recent ship velocity. Browse the "vellum alternatives" section above for the current picks, or visit /alternatives/vellum-r for the full list with editorial commentary on each.