← Back to home
Comparison · Analytics

ducksemantics vs vellumwidget

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

ducksemantics vs vellumwidget: at a glance

Featureducksemanticsvellumwidget
SectorAnalyticsAnalytics
Velocity score2.56.3
Sparks · 30d01
Top themesduckdb, semantic search, ontologies, retrievalr-graphics, interactive-widgets, declarative-interaction, shiny
Last editorial update13m ago1h ago
WebsiteVisit →Visit →

What is ducksemantics?

ducksemantics puts an ontology graph and ColBERT retrieval inside DuckDB, callable from R.

ducksemantics is a first release, and an unusually complete one. It combines a DuckDB-native semantic graph, lexical grounding, dense retrieval, exact late-interaction scoring, and structured judgment behind a single R API. The release notes report a full HPO ontology load of 19,836 nodes with 202,740 materialized is_a closure rows, plus persisted EmbeddingGemma and LFM2.5-ColBERT vectors, with DuckDB MaxSim agreeing with an external implementation to seven decimal places.

Read the full ducksemantics trajectory →

What is vellumwidget?

vellumwidget is dissolving its own API: interaction now lives in the plot spec, not the widget call.

vellumwidget compiles a vellum scene or a vellumplot plot into a self-contained client-side htmlwidget with hover, select, brush, lasso, pan/zoom and export, and no server round-trip. The two-way Shiny story is complete: interactions surface as reactive inputs keyed by output id, and vellumwidget_proxy() drives an already-rendered widget from the server without re-rendering it. The last two releases are fidelity work rather than new surface, calibrating hit-testing from the rendered positions of marks and rendering the raster base image at 2x for HiDPI screens.

Read the full vellumwidget trajectory →

ducksemantics vs vellumwidget: editorial side-by-side

D
ducksemantics
ANALYTICS
2.5

ducksemantics puts an ontology graph and ColBERT retrieval inside DuckDB, callable from R.

◆ Current state

ducksemantics is a first release, and an unusually complete one. It combines a DuckDB-native semantic graph, lexical grounding, dense retrieval, exact late-interaction scoring, and structured judgment behind a single R API. The release notes report a full HPO ontology load of 19,836 nodes with 202,740 materialized is_a closure rows, plus persisted EmbeddingGemma and LFM2.5-ColBERT vectors, with DuckDB MaxSim agreeing with an external implementation to seven decimal places.

◆ Where it's heading

With one release on the record there is no trend to read, only a stated posture: correctness first. The release documents transactional and idempotent graph writes, atomic and resumable embedding caches, index preservation across graph projection, and a verified numerical match against a reference MaxSim implementation. That is the profile of a package expecting to be used as infrastructure rather than a demo.

◆ Prediction

Where this goes next is not yet determinable from a single release. The obvious pressure point is ontology coverage beyond the HPO used for validation, but the entries do not indicate a plan.

V
vellumwidget
ANALYTICS
6.3

vellumwidget is dissolving its own API: interaction now lives in the plot spec, not the widget call.

◆ Current state

vellumwidget compiles a vellum scene or a vellumplot plot into a self-contained client-side htmlwidget with hover, select, brush, lasso, pan/zoom and export, and no server round-trip. The two-way Shiny story is complete: interactions surface as reactive inputs keyed by output id, and vellumwidget_proxy() drives an already-rendered widget from the server without re-rendering it. The last two releases are fidelity work rather than new surface, calibrating hit-testing from the rendered positions of marks and rendering the raster base image at 2x for HiDPI screens.

◆ Where it's heading

The direction is declarative. 0.7.0 removed the interaction-intent arguments from as_widget() outright, dropping the signature from roughly 36 arguments to 24 and moving highlight, filter and cross-filter into vellumplot's spec via select_point(), condition() and filter_by(). Each release since has enacted more of that compiled spec on the frozen scene, from conditional encodings to single-view filters to cross-view cross-filtering, leaving the widget as an interpreter of the plot rather than a configuration surface of its own. The bug fixes track the same theme the engine's do: measured geometry and rendered geometry must not drift.

◆ Prediction

The notes name the remaining hold-outs explicitly, saying hover_mode, crosshair, legend_click, select_mode and the tooltip-appearance arguments remain only until their spec equivalents land, so the next releases most likely move those into vellumplot and shrink as_widget() further. The scale binds flagged as following the filter work are the other stated next step.

Alternatives to ducksemantics and vellumwidget

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 ducksemantics or vellumwidget.

See all ducksemantics alternatives → · See all vellumwidget alternatives →

Recent activity from ducksemantics and vellumwidget

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

  1. 14d agovellumwidget2x raster base image for HiDPI, and exact element hit-testing
  2. 20d agovellumwidgetInteraction moves into the plot spec; as_widget() sheds a third of its arguments
  3. 26d agoducksemanticsFirst release: DuckDB-native semantic graph and retrieval
  4. 27d agovellumwidgetAxis-aware zoom re-ticks the axes instead of scaling the whole scene
  5. 1mo agovellumwidgetSelectable native SVG text, and crisp canvas redraw when zooming raster
  6. 1mo agovellumwidgetServer-side proxy drives a rendered widget without re-rendering it
  7. 1mo agovellumwidgetShiny input read-back, and keyboard plus screen-reader access by default

Frequently asked questions

What is the difference between ducksemantics and vellumwidget?

They serve adjacent needs but don't currently overlap on shipped themes. vellumwidget is currently shipping more aggressively (velocity 6.3 vs 2.5), 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 ducksemantics better than vellumwidget?

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

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

What are the best alternatives to vellumwidget?

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