← Back to home
Comparison · Analytics

gigs vs textshaping

A side-by-side editorial comparison of gigs and textshaping — release velocity, themes, recent moves, and the top alternatives to consider.

Shared themes:r-package

gigs vs textshaping: at a glance

Featuregigstextshaping
SectorAnalyticsAnalytics
Velocity score0.00.0
Sparks · 30d00
Top themesgrowth-standards, neonatal-health, r-package, ropenscitypography, text-shaping, bidi, graphics-stack
Last editorial update56m ago4h ago
WebsiteVisit →Visit →

What is gigs?

gigs redesigned its whole conversion API for rOpenSci, then spent three releases getting the docs to build.

gigs implements international newborn and infant growth standards — INTERGROWTH-21st, WHO — converting anthropometric measurements to z-scores and centiles and classifying growth outcomes. The 0.5.0 release rewrote the public API around rOpenSci review feedback; the two releases after it change no code at all, existing purely to get the documentation site building.

Read the full gigs trajectory →

What is textshaping?

Rewrote its shaping engine for bidirectional text, then spent a year fixing what that broke.

textshaping is the text layout layer beneath R's modern graphics stack, feeding ragg, ggplot2 and marquee. Version 1.0.0 rewrote the shaping engine to honour the global direction of text, adding a direction argument that defaults to automatic detection, align settings that resolve against that direction, and ICU-based soft break locations that handle ideographic scripts properly. The five releases since have been consecutive bug fixes against that rewrite — bidi embedding arrangement, line positioning with mixed sizes, a weak hash in the shape cache, a signed integer overflow, and font fallback regressions.

Read the full textshaping trajectory →

gigs vs textshaping: editorial side-by-side

G
gigs
ANALYTICS
0.0

gigs redesigned its whole conversion API for rOpenSci, then spent three releases getting the docs to build.

◆ Current state

gigs implements international newborn and infant growth standards — INTERGROWTH-21st, WHO — converting anthropometric measurements to z-scores and centiles and classifying growth outcomes. The 0.5.0 release rewrote the public API around rOpenSci review feedback; the two releases after it change no code at all, existing purely to get the documentation site building.

◆ Where it's heading

The package has moved from vector-in, vector-out conversion helpers to a data.frame-oriented interface with a single classify_growth() entry point that computes whatever outcomes the supplied columns allow. That is a shift from library to tool — the user describes their data rather than picking the right function. The trailing releases suggest the code is settled and the remaining work is packaging and discoverability.

◆ Prediction

With the API rewrite absorbed and hosting moved to rOpenSci, the next substantive release should add growth standards or outcomes rather than reshape the interface again.

T
textshaping
ANALYTICS
0.0

Rewrote its shaping engine for bidirectional text, then spent a year fixing what that broke.

◆ Current state

textshaping is the text layout layer beneath R's modern graphics stack, feeding ragg, ggplot2 and marquee. Version 1.0.0 rewrote the shaping engine to honour the global direction of text, adding a direction argument that defaults to automatic detection, align settings that resolve against that direction, and ICU-based soft break locations that handle ideographic scripts properly. The five releases since have been consecutive bug fixes against that rewrite — bidi embedding arrangement, line positioning with mixed sizes, a weak hash in the shape cache, a signed integer overflow, and font fallback regressions.

◆ Where it's heading

The package has moved from Latin-first layout to script-agnostic layout in two rewrites, 0.4.0 and 1.0.0, and is now in the long correctness tail that follows. The bug reports arriving from ggplot2, ragg and marquee issue numbers show how it works in practice: textshaping bugs surface as rendering defects in the packages above it, which is why so many fixes here cite another package's issue tracker.

◆ Prediction

Expect continued fixes driven by downstream rendering reports rather than new layout features, as the 1.0.x series stabilises. The font fallback path has produced two of the recent bugs and is the most likely source of the next.

Alternatives to gigs and textshaping

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 gigs or textshaping.

See all gigs alternatives → · See all textshaping alternatives →

Recent activity from gigs and textshaping

Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.

  1. 5mo agotextshapingFixes reverting between font fallbacks
  2. 9mo agotextshapingGuards against freetype version mismatches with systemfonts
  3. 11mo agotextshapingFixes a signed integer overflow in the previous fix
  4. 11mo agotextshapingFixes bidi single-line shaping and a weak shape-cache hash
  5. 1y agotextshapingFixes hard line breaks across multiple embeddings
  6. 1y agogigsDocs and Zenodo archiving
  7. 1y agotextshapingShaping engine rewritten to honour global text direction
  8. 1y agogigsDocs-only release; nothing changed internally
  9. 1y agogigsConversion API rewritten around data frames and classify_growth()
  10. 2y agogigsDocumentation fixes for autotest compliance
  11. 2y agogigsINTERGROWTH-21st fetal standards and input validation
  12. 2y agogigsPatch release with documentation update

Frequently asked questions

What is the difference between gigs and textshaping?

Both compete on the same themes — r-package — within Analytics. gigs and textshaping 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.

Is gigs better than textshaping?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. gigs and textshaping 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.

What are the best alternatives to gigs?

Top gigs alternatives in Analytics are ranked by recent ship velocity. Browse the "gigs alternatives" section above for the current picks, or visit /alternatives/gigs for the full list with editorial commentary on each.

What are the best alternatives to textshaping?

Top textshaping alternatives in Analytics are ranked by recent ship velocity. Browse the "textshaping alternatives" section above for the current picks, or visit /alternatives/textshaping for the full list with editorial commentary on each.