gps2gtfs
gps2gtfs spent a release making its docs stop describing functions it does not have.
Comparison · Analytics
glydet vs vellumwidget
A side-by-side editorial comparison of glydet and vellumwidget — release velocity, themes, recent moves, and the top alternatives to consider.
glydet vs vellumwidget: at a glance
What is glydet?
glydet is rebuilding its glycan trait vocabulary on top of someone else's container.
glydet derives glycan-derived traits from glycomics and glycoproteomics data. The 0.12.x line spent its releases absorbing glyexp's container migration: derive_traits(), quantify_motifs(), and add_meta_properties() now accept GlycomicSE and GlycoproteomicSE natively, with the legacy experiment() path kept only for backward-compatible return types. The substantive feature work sits one release back in 0.11.0, which added sialic acid linkage traits and three published trait sets.
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.
glydet vs vellumwidget: editorial side-by-side
glydet
0.0ANALYTICS
glydet is rebuilding its glycan trait vocabulary on top of someone else's container.
◆ Current state
glydet derives glycan-derived traits from glycomics and glycoproteomics data. The 0.12.x line spent its releases absorbing glyexp's container migration: derive_traits(), quantify_motifs(), and add_meta_properties() now accept GlycomicSE and GlycoproteomicSE natively, with the legacy experiment() path kept only for backward-compatible return types. The substantive feature work sits one release back in 0.11.0, which added sialic acid linkage traits and three published trait sets.
◆ Where it's heading
Two threads run in parallel here. One is infrastructure: track glyexp's Stage II migration, drop the underscore matrix interfaces, and converge on a single trait column in var_info. The other is content: keep adding named trait sets from the literature (Clerc 2018, Li 2025, Fu 2026) so users cite a set rather than hand-roll definitions. The LLM-backed explain_trait() and make_trait() helpers are becoming provider-agnostic rather than deeper.
◆ Prediction
The trait catalogue is the growth area, so expect more published trait sets added as named functions, and the deprecated basic_traits() and all_traits() aliases to be removed once the container migration settles.
vellumwidget
6.3ANALYTICS
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 glydet 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 glydet or vellumwidget.
ducksemantics
ducksemantics puts an ontology graph and ColBERT retrieval inside DuckDB, callable from R.
dvir
dvir keeps making disaster victim identification a single call instead of a workflow.
pedbuildr
pedbuildr reconstructs pedigrees from DNA, and it just got much faster at the search.
forrel
forrel is getting faster at the simulations forensic kinship work actually spends its time on.
pedFamilias
pedFamilias exists to read one legacy file format, and it has that job nearly finished.
See all glydet alternatives → · See all vellumwidget alternatives →
Recent activity from glydet and vellumwidget
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 14d agovellumwidget2x raster base image for HiDPI, and exact element hit-testing
- 20d agovellumwidgetInteraction moves into the plot spec; as_widget() sheds a third of its arguments ⚡
- 27d agovellumwidgetAxis-aware zoom re-ticks the axes instead of scaling the whole scene
- 1mo agovellumwidgetSelectable native SVG text, and crisp canvas redraw when zooming raster
- 1mo agoglydetDocs and vignettes move to SummarizedExperiment inputs
- 1mo agoglydetTrait functions behave consistently across both containers
- 1mo agovellumwidgetServer-side proxy drives a rendered widget without re-rendering it
- 1mo agoglydetContainer migration lands alongside batch trait creation
- 1mo agovellumwidgetShiny input read-back, and keyboard plus screen-reader access by default
- 1mo agoglydetglymotif 0.17 compatibility and clearer trait wording
- 3mo agoglydetSialic acid linkage traits and three published trait sets
- 4mo agoglydetVariable name standardization and vignette fixes
Frequently asked questions
What is the difference between glydet and vellumwidget?
They serve adjacent needs but don't currently overlap on shipped themes. vellumwidget is currently shipping more aggressively (velocity 6.3 vs 0.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 glydet 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 0.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 glydet?
Top glydet alternatives in Analytics are ranked by recent ship velocity. Browse the "glydet alternatives" section above for the current picks, or visit /alternatives/glydet 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.