glyfun
glyfun is three releases old and has spent all of them chasing glyexp's container change.
A side-by-side editorial comparison of qqman and vellumwidget — release velocity, themes, recent moves, and the top alternatives to consider.
The Manhattan-plot package for GWAS results, finished and dormant since 2017.
qqman does two things: manhattan() and qq() plots for genome-wide association study results. Its six visible releases run from 2014 to a single 2017 packaging fix, and the last release with any user-facing change shipped in 2015. The archive is non-monotonic — a 0.0.0 tag published after 0.1.1 archives the pre-package standalone script — so version order and publication order disagree.
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.
qqman does two things: manhattan() and qq() plots for genome-wide association study results. Its six visible releases run from 2014 to a single 2017 packaging fix, and the last release with any user-facing change shipped in 2015. The archive is non-monotonic — a 0.0.0 tag published after 0.1.1 archives the pre-package standalone script — so version order and publication order disagree.
The real development window was 2014 to 2015. The 0.1.2 release did the substantive work, replacing the assumption that SNPs are evenly distributed across chromosomes and handing users control of axis limits, labels and log transformation; 0.1.3 then added annotation by p-value threshold and top-SNP-per-chromosome. After that the package stops. Notably, the archival 0.0.0 entry records that the original script had confidence intervals on QQ plots and richer highlighting than the released package ever regained.
With one packaging fix in the last decade, these entries support no prediction of further releases. The package reads as complete for its narrow purpose rather than abandoned mid-arc.
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.
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.
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.
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 qqman or vellumwidget.
glyfun is three releases old and has spent all of them chasing glyexp's container change.
glydet is rebuilding its glycan trait vocabulary on top of someone else's container.
glyexp is retiring its own data container and handing the job to Bioconductor.
A glycan motif matcher trading convenience wrappers for speed, strictness and explicit specs.
The type system the rest of the glycan stack is built on, being hardened one breaking change at a time.
Glycan annotation stops depending on the database having seen the structure before.
See all qqman alternatives → · See all vellumwidget alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
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.
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.
Top qqman alternatives in Analytics are ranked by recent ship velocity. Browse the "qqman alternatives" section above for the current picks, or visit /alternatives/qqman-r for the full list with editorial commentary on each.
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.