spsurvey
spsurvey has spent four years consolidating after its 5.0.0 rewrite rather than adding to it
Comparison · Analytics
glyanno vs tibblify
A side-by-side editorial comparison of glyanno and tibblify — release velocity, themes, recent moves, and the top alternatives to consider.
glyanno vs tibblify: at a glance
What is glyanno?
Glycan annotation stops depending on the database having seen the structure before.
glyanno resolves mass spectrometry observations into glycan compositions and structures, converting between m/z, composition and structure, filling in missing detail on partial structures, and mapping results to GlyTouCan accessions. The newest release adds de novo reconstruction of topological N-glycans, falling back to the topological database only when reconstruction is not possible. Batch performance was reworked at the same time, with vector inputs reusing prepared databases and direct lookups instead of repeating setup per element.
What is tibblify?
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.
glyanno vs tibblify: editorial side-by-side
glyanno
3.8ANALYTICS
Glycan annotation stops depending on the database having seen the structure before.
◆ Current state
glyanno resolves mass spectrometry observations into glycan compositions and structures, converting between m/z, composition and structure, filling in missing detail on partial structures, and mapping results to GlyTouCan accessions. The newest release adds de novo reconstruction of topological N-glycans, falling back to the topological database only when reconstruction is not possible. Batch performance was reworked at the same time, with vector inputs reusing prepared databases and direct lookups instead of repeating setup per element.
◆ Where it's heading
The consistent theme is making ambiguous results honest and predictable. return_best moved from returning a shortened tibble to a vector aligned with the input, with NA for unmatched glycans; matching concrete compositions against a generic database now errors instead of silently returning nothing; zero-length database arguments are rejected. Alongside that, functions belonging elsewhere have been pushed down into glyrepr rather than duplicated, which is the same boundary discipline visible across this cohort. Version churn is largely driven by upstream: two of the last six entries exist to absorb breaking changes in glyrepr.
◆ Prediction
De novo reconstruction currently covers topological N-glycans only, so extending it to other structure levels or to O-glycans is the natural next step. The performance work suggests batch annotation of full experiments is now the primary use being optimised for.
tibblify
0.0ANALYTICS
tibblify learned to derive its own specs from OpenAPI, removing the step users disliked most
◆ Current state
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.
◆ Where it's heading
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.
◆ Prediction
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.
Alternatives to glyanno and tibblify
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 glyanno or tibblify.
StreamCatTools
StreamCatTools is quietly moving off web services and onto cloud-native GeoParquet
reproducible
reproducible added a windowed read path so remote GeoTiffs never fully download
qcTAF
qcTAF is building an automated checklist for reproducible fisheries assessments, one criterion at a time
rpymat
After three dormant years, rpymat returned to fix the OpenMP crash that breaks R and conda together
ieegio
ieegio's first release lands electrode trajectory burning and a WebGL-free surface plot
See all glyanno alternatives → · See all tibblify alternatives →
Recent activity from glyanno and tibblify
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 24d agoglyannoDe novo reconstruction of topological N-glycans, with database fallback ⚡
- 3mo agotibblifyFix type mismatch in C code
- 3mo agotibblifyDot-prefixed arguments and a full internal refactor
- 3mo agoglyannoGlyTouCan accession mapping and anomeric position filling
- 3mo agoglyannoFixes an enhance_struc() break from glyrepr 0.11.0
- 4mo agoglyannoExplicit empty return from com_to_struc()
- 4mo agoglyannoreturn_best output aligns with input length; silent empty matches now error
- 5mo agoglyannoto_level parameter removed from enhance_struc()
- 2y agotibblifyparse_openapi_spec() generates tibblify specs from API documentation ⚡
- 3y agotibblifyRecursive specs, transform control and memory fixes
- 4y agotibblifyEngine rewritten in C with a renamed specification API ⚡
Frequently asked questions
What is the difference between glyanno and tibblify?
They serve adjacent needs but don't currently overlap on shipped themes. glyanno is currently shipping more aggressively (velocity 3.8 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 glyanno better than tibblify?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. glyanno is currently shipping more aggressively (velocity 3.8 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 glyanno?
Top glyanno alternatives in Analytics are ranked by recent ship velocity. Browse the "glyanno alternatives" section above for the current picks, or visit /alternatives/glyanno for the full list with editorial commentary on each.
What are the best alternatives to tibblify?
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.