← Back to home
Comparison · Analytics

S7 vs textshaping

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

S7 vs textshaping: at a glance

FeatureS7textshaping
SectorAnalyticsAnalytics
Velocity score0.00.0
Sparks · 30d00
Top themesobject-system, r-language, api-stability, backward-compatibilitytypography, text-shaping, bidi, graphics-stack
Last editorial update44m ago2h ago
WebsiteVisit →Visit →

What is S7?

S7 has stopped adding surface and started proving it holds up against R itself.

S7 is R's third-generation object system, built to unify the S3 and S4 lineages rather than add a fourth. The design work landed in 0.2.0, which reworked the default constructor, extended base-class coverage, and added a backward-compatibility shim so `@` property access works on R older than 4.3. Everything since has been maintenance: property setters gained a `check` escape hatch, and two consecutive releases exist mainly to keep the package compiling against R-devel 4.6.

Read the full S7 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 →

S7 vs textshaping: editorial side-by-side

S
S7
ANALYTICS
0.0

S7 has stopped adding surface and started proving it holds up against R itself.

◆ Current state

S7 is R's third-generation object system, built to unify the S3 and S4 lineages rather than add a fourth. The design work landed in 0.2.0, which reworked the default constructor, extended base-class coverage, and added a backward-compatibility shim so `@` property access works on R older than 4.3. Everything since has been maintenance: property setters gained a `check` escape hatch, and two consecutive releases exist mainly to keep the package compiling against R-devel 4.6.

◆ Where it's heading

The changelog is thinning by design — 0.1.0 was a months-long feature dump, 0.2.0 a coordinated architectural revision, 0.2.2 a single line about internal R-devel support. That shape usually means an API the maintainers consider settled, where the remaining work is tracking the host language rather than extending the system. The one recurring theme is validation cost: repeated releases have made validation less frequent, more targeted, or skippable outright.

◆ Prediction

Expect continued small releases pinned to R-devel changes rather than new class-system features, with any further movement most likely in the validation and property-setter path that the last two feature changes both touched.

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

See all S7 alternatives → · See all textshaping alternatives →

Recent activity from S7 and textshaping

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

  1. 3mo agoS7Internal fixes for R-devel 4.6 compatibility
  2. 5mo agotextshapingFixes reverting between font fallbacks
  3. 9mo agoS7Property setters gain an opt-out from validation
  4. 9mo agotextshapingGuards against freetype version mismatches with systemfonts
  5. 11mo agotextshapingFixes a signed integer overflow in the previous fix
  6. 11mo agotextshapingFixes bidi single-line shaping and a weak shape-cache hash
  7. 1y agotextshapingFixes hard line breaks across multiple embeddings
  8. 1y agotextshapingShaping engine rewritten to honour global text direction
  9. 1y agoS7Constructor rework and pre-4.3 support for @ access
  10. 2y agoS7Per-property validators and better S3 method registration
  11. 2y agoS7First release: unions, set_props, and S4 virtual dispatch

Frequently asked questions

What is the difference between S7 and textshaping?

They serve adjacent needs but don't currently overlap on shipped themes. S7 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 S7 better than textshaping?

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

Top S7 alternatives in Analytics are ranked by recent ship velocity. Browse the "S7 alternatives" section above for the current picks, or visit /alternatives/s7 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.