spsurvey
spsurvey has spent four years consolidating after its 5.0.0 rewrite rather than adding to it
A side-by-side editorial comparison of glymotif and tibblify — release velocity, themes, recent moves, and the top alternatives to consider.
A glycan motif matcher trading convenience wrappers for speed, strictness and explicit specs.
glymotif detects and counts structural motifs in glycans, over a built-in motif database or user-supplied structures, with fuzzy modification matching and alignment control. Database motifs are now requested through a db_motifs_spec object carrying their own matching parameters rather than as a name vector with loose arguments, and db_motif_info() exposes the built-in set as an inspectable tibble. A lenient mode lets lower-information glycans match more specific motifs while concrete mismatches still fail, and low-level entry points work directly on igraph objects for other package authors.
tibblify learned to derive its own specs from OpenAPI, removing the step users disliked most
tibblify converts nested lists and JSON into rectangular tibbles using an explicit specification of the expected structure. Its 0.2.0 rewrite moved the engine to C and reset the API; 0.3.1 then added a path to generate specifications from an OpenAPI document rather than hand-writing them. 0.4.0 in May 2026 is the first release in over two years, and it is a breaking cleanup.
glymotif detects and counts structural motifs in glycans, over a built-in motif database or user-supplied structures, with fuzzy modification matching and alignment control. Database motifs are now requested through a db_motifs_spec object carrying their own matching parameters rather than as a name vector with loose arguments, and db_motif_info() exposes the built-in set as an inspectable tibble. A lenient mode lets lower-information glycans match more specific motifs while concrete mismatches still fail, and low-level entry points work directly on igraph objects for other package authors.
Performance has been a recurring line item across at least four releases, culminating in optimised graph searches and candidate filtering aimed at batch analyses, which points at the real workload being whole experiments rather than single glycans. The API has moved the other way from convenience toward explicitness: the add_motifs_lgl() and add_motifs_int() wrappers are deprecated in favour of composing with dplyr or glyexp verbs, optional arguments must now be named, and loose matching parameters were folded into the spec object. Documentation is being steered toward the cohort's newer container types, so this package is following a coordinated migration rather than setting its own course.
With the deprecated annotation wrappers on their way out and documentation already pointing at the replacement verbs, their removal is the likely next breaking change. The lenient matching mode is new enough that its boundary against concrete mismatches will probably need tuning as users apply it to real, partially resolved data.
tibblify converts nested lists and JSON into rectangular tibbles using an explicit specification of the expected structure. Its 0.2.0 rewrite moved the engine to C and reset the API; 0.3.1 then added a path to generate specifications from an OpenAPI document rather than hand-writing them. 0.4.0 in May 2026 is the first release in over two years, and it is a breaking cleanup.
The arc runs from 'write a spec by hand' toward 'the spec comes from somewhere else'. Alongside the OpenAPI importer, guess_tspec() gained exported variants so users can override its dispatch, and untibblify() now picks up the tib_spec attribute automatically. 0.4.0's breaking change prefixes all arguments of dot-accepting functions with a period to avoid collisions with column names, softened by a once-per-session deprecation warning, and refactors the entire codebase.
The un-dotted argument forms are explicitly slated for removal, so the next release most likely completes that deprecation. Whether the 0.4.0 refactor introduced corner-case regressions is the open question the release notes themselves raise.
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 glymotif or tibblify.
spsurvey has spent four years consolidating after its 5.0.0 rewrite rather than adding to it
StreamCatTools is quietly moving off web services and onto cloud-native GeoParquet
reproducible added a windowed read path so remote GeoTiffs never fully download
qcTAF is building an automated checklist for reproducible fisheries assessments, one criterion at a time
After three dormant years, rpymat returned to fix the OpenMP crash that breaks R and conda together
ieegio's first release lands electrode trajectory burning and a WebGL-free surface plot
See all glymotif alternatives → · See all tibblify alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. glymotif is currently shipping more aggressively (velocity 2.5 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. glymotif is currently shipping more aggressively (velocity 2.5 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 glymotif alternatives in Analytics are ranked by recent ship velocity. Browse the "glymotif alternatives" section above for the current picks, or visit /alternatives/glymotif for the full list with editorial commentary on each.
Top tibblify alternatives in Analytics are ranked by recent ship velocity. Browse the "tibblify alternatives" section above for the current picks, or visit /alternatives/tibblify for the full list with editorial commentary on each.