tibblify
tibblify learned to derive its own specs from OpenAPI, removing the step users disliked most
A side-by-side editorial comparison of glyparse and pedFamilias — release velocity, themes, recent moves, and the top alternatives to consider.
glyparse is quietly becoming the universal reader for glycan text notation.
glyparse converts the various text encodings of glycan structures into glyrepr objects. Version 0.7.0 was the widest release in the window, adding parsers for GlyCAM IUPAC, IUPAC-compact, KCF, and LINUCS and teaching auto_parse() to route them, alongside a long list of GlycoCT and WURCS edge cases. The rest of the window is error-handling and performance work: an on_failure switch, a 10-30x speedup on large inputs, and NA and name preservation.
pedFamilias exists to read one legacy file format, and it has that job nearly finished.
pedFamilias holds the Familias file interoperability code that was split out of forrel, principally readFam() and writeFam(). The visible history is short and narrow: URL paths accepted as input, a deduplicate option for files produced by the Familias DVI module, better handling of extra individuals, and a fallback mutation model when stabilization fails. The most recent release is explicitly maintenance.
glyparse converts the various text encodings of glycan structures into glyrepr objects. Version 0.7.0 was the widest release in the window, adding parsers for GlyCAM IUPAC, IUPAC-compact, KCF, and LINUCS and teaching auto_parse() to route them, alongside a long list of GlycoCT and WURCS edge cases. The rest of the window is error-handling and performance work: an on_failure switch, a 10-30x speedup on large inputs, and NA and name preservation.
Two things are being built at once. Coverage keeps widening, both in the number of notations supported and in how much malformed or ambiguous real-world input each parser tolerates: alditol residues, unknown ring positions, ambiguous sialic acid descriptors, uppercase residue IDs. Meanwhile the package is hardening for batch use, with progress bars, vectorized speed, and a choice between erroring and returning NA on unparsable strings.
With the major notations now covered, expect further releases to go to robustness on messy inputs and to keeping pace with glyrepr's structure representation rather than adding formats.
pedFamilias holds the Familias file interoperability code that was split out of forrel, principally readFam() and writeFam(). The visible history is short and narrow: URL paths accepted as input, a deduplicate option for files produced by the Familias DVI module, better handling of extra individuals, and a fallback mutation model when stabilization fails. The most recent release is explicitly maintenance.
This is a package with a bounded remit. The format it parses does not change, so releases arrive only when someone encounters a file it mishandles, and the fixes are correspondingly specific. The interesting movement is upstream instead: forrel finally removed its deprecated readFam() re-export in 1.9.0, completing the split that created this package.
Expect continued low-frequency maintenance driven by real-world .fam files rather than any planned feature work.
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 glyparse or pedFamilias.
tibblify learned to derive its own specs from OpenAPI, removing the step users disliked most
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
See all glyparse alternatives → · See all pedFamilias alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — file formats, r packages — within Analytics. glyparse and pedFamilias are shipping at a similar cadence (velocity 0.0 vs 0.0, both within Sparkpulse's "active" band). 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. glyparse and pedFamilias are shipping at a similar cadence (velocity 0.0 vs 0.0, both within Sparkpulse's "active" band). For your specific use case, the alternatives sections above list other Analytics products to evaluate alongside.
Top glyparse alternatives in Analytics are ranked by recent ship velocity. Browse the "glyparse alternatives" section above for the current picks, or visit /alternatives/glyparse for the full list with editorial commentary on each.
Top pedFamilias alternatives in Analytics are ranked by recent ship velocity. Browse the "pedFamilias alternatives" section above for the current picks, or visit /alternatives/pedfamilias for the full list with editorial commentary on each.