← Back to home
Comparison · Analytics

vellum vs vellumplot

A side-by-side editorial comparison of vellum and vellumplot — release velocity, themes, recent moves, and the top alternatives to consider.

Shared themes:r-graphicsaccessibility

vellum vs vellumplot: at a glance

Featurevellumvellumplot
SectorAnalyticsAnalytics
Velocity score5.06.3
Sparks · 30d01
Top themesr-graphics, rendering-engine, linting, accessibilityr-graphics, grammar-of-graphics, accessibility, data-visualization
Last editorial update1h ago1h ago
WebsiteVisit →Visit →

What is vellum?

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.

Read the full vellum trajectory →

What is vellumplot?

vellumplot tags its first release with a bet most R grammars don't make: the static figure and the widget are the same object.

A new grammar of graphics built on the vellum vector engine, developing fast — ten releases in roughly three weeks — and now at its first tagged release. The distinguishing architectural claim is that the compiled plot is the scene, so a static export and an interactive widget cannot drift apart, and that it renders without a graphics device because vellum measures text itself. Accessibility is treated as a first-class output rather than an afterthought: tagged PDF with a navigable structure tree and alt text, a plot_lint() check, and colour-vision-deficiency simulation at render time.

Read the full vellumplot trajectory →

vellum vs vellumplot: editorial side-by-side

V
vellum
ANALYTICS
5.0

vellum's bugs are now found by using it, not testing it — the downstream grammar is doing the QA.

◆ Current state

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.

◆ Where it's heading

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.

◆ Prediction

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.

V
vellumplot
ANALYTICS
6.3

vellumplot tags its first release with a bet most R grammars don't make: the static figure and the widget are the same object.

◆ Current state

A new grammar of graphics built on the vellum vector engine, developing fast — ten releases in roughly three weeks — and now at its first tagged release. The distinguishing architectural claim is that the compiled plot is the scene, so a static export and an interactive widget cannot drift apart, and that it renders without a graphics device because vellum measures text itself. Accessibility is treated as a first-class output rather than an afterthought: tagged PDF with a navigable structure tree and alt text, a plot_lint() check, and colour-vision-deficiency simulation at render time.

◆ Where it's heading

The release sequence shows a grammar filling in ggplot2-parity features and specialist marks in parallel. Parity work landed as secondary axes, rich legend titles, and Sankey styling; the specialist end added categorical datashading, image marks, flow maps and edge bundling for dense graphs. Version 0.7.0 shows a willingness to break early — vsunburst() was removed outright in favour of one vhierarchy() constructor covering sunburst, icicle, treemap and circlepack — which is the right time to do it and suggests the API is still being consolidated toward fewer, more general constructors.

◆ Prediction

Expect more consolidation of near-duplicate constructors under type arguments and continued expansion of the declarative interactivity introduced in 0.7.0, now that the first tagged release has fixed a public API surface.

Alternatives to vellum and vellumplot

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 vellum or vellumplot.

See all vellum alternatives → · See all vellumplot alternatives →

Recent activity from vellum and vellumplot

Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.

  1. 11d agovellumLinter grows to 20 rules and stops firing on every plot
  2. 13d agovellumAnimated SVGs no longer blink once and vanish or play in reverse
  3. 13d agovellumPick table now reports device pixels instead of two coordinate systems
  4. 14d agovellumplotFirst tagged release: one spec compiles to PNG, SVG, tagged PDF and a widget
  5. 14d agovellumContrast rule stops flagging every plot; gridlines become PDF artifacts
  6. 14d agovellumgrobwidth and grobheight now measure wrapped text, not the unwrapped line
  7. 15d agovellumKeyed roundrect becomes a real batch after downstream integration exposes it
  8. 19d agovellumplotFlow maps and edge bundling for dense graph plots
  9. 24d agovellumplotvhierarchy() replaces vsunburst(); declarative interactivity arrives
  10. 26d agovellumplotSankey crossing minimisation and per-branch sunburst colouring
  11. 29d agovellumplotSecondary axes land; rich legend titles stop clipping
  12. 1mo agovellumplotCategorical datashading in one call, plus image marks at data points

Frequently asked questions

What is the difference between vellum and vellumplot?

Both compete on the same themes — r-graphics, accessibility — within Analytics. vellumplot is currently shipping more aggressively (velocity 6.3 vs 5.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 vellum better than vellumplot?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. vellumplot is currently shipping more aggressively (velocity 6.3 vs 5.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 vellum?

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.

What are the best alternatives to vellumplot?

Top vellumplot alternatives in Analytics are ranked by recent ship velocity. Browse the "vellumplot alternatives" section above for the current picks, or visit /alternatives/vellumplot for the full list with editorial commentary on each.