← Back to home
Comparison · Analytics

textshaping vs vcr

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

textshaping vs vcr: at a glance

Featuretextshapingvcr
SectorAnalyticsAnalytics
Velocity score0.00.0
Sparks · 30d00
Top themestypography, text-shaping, bidi, graphics-stacktesting, http-mocking, breaking-change, api-cleanup
Last editorial update1h ago1h ago
WebsiteVisit →Visit →

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 →

What is vcr?

Added the HTTP client everyone moved to, then deleted a decade of its own public surface.

vcr records HTTP interactions to disk so R package tests can replay them without network access. Two releases define its current state. Version 1.6.0 added httr2 support alongside the existing httr and crul backends, following the R ecosystem's migration to httr2. Version 2.0 then removed a large amount of accumulated public surface — the logging functions, vcr_last_error(), the exported R6 classes including RequestHandler, Request, VcrResponse and HTTPInteractionList, and several configuration options that had stopped working or could not be implemented correctly.

Read the full vcr trajectory →

textshaping vs vcr: editorial side-by-side

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.

V
vcr
ANALYTICS
0.0

Added the HTTP client everyone moved to, then deleted a decade of its own public surface.

◆ Current state

vcr records HTTP interactions to disk so R package tests can replay them without network access. Two releases define its current state. Version 1.6.0 added httr2 support alongside the existing httr and crul backends, following the R ecosystem's migration to httr2. Version 2.0 then removed a large amount of accumulated public surface — the logging functions, vcr_last_error(), the exported R6 classes including RequestHandler, Request, VcrResponse and HTTPInteractionList, and several configuration options that had stopped working or could not be implemented correctly.

◆ Where it's heading

The package is consolidating after years of additive growth. The 2.0 removals are almost all things that were exported without needing to be, or options that promised behaviour the implementation could not guarantee — check_cassette_names() was deprecated precisely because it cannot be made correct. Cassette maintenance is being simplified too, with re_record_interval now the single mechanism for expiring recordings.

◆ Prediction

Expect the post-2.0 releases to be about migration support and fallout from the removed API, since the breaking list is long enough that reverse dependencies will surface problems. Async support for httr2 stays blocked until req_perform_parallel gains a mocking hook, which the entries note is upstream work.

Alternatives to textshaping and vcr

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

See all textshaping alternatives → · See all vcr alternatives →

Recent activity from textshaping and vcr

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

  1. 5mo agotextshapingFixes reverting between font fallbacks
  2. 8mo agovcr2.0 removes the logging API and the exported R6 classes
  3. 9mo agotextshapingGuards against freetype version mismatches with systemfonts
  4. 11mo agotextshapingFixes a signed integer overflow in the previous fix
  5. 11mo agotextshapingFixes bidi single-line shaping and a weak shape-cache hash
  6. 1y agotextshapingFixes hard line breaks across multiple embeddings
  7. 1y agovcrMaintainer email address updated
  8. 1y agotextshapingShaping engine rewritten to honour global text direction
  9. 2y agovcrAdds httr2 support alongside httr and crul
  10. 3y agovcrDrops compilation; test setup moves back to helper files
  11. 3y agovcrFixes request matching with escaped characters
  12. 5y agovcrvcr_test_path() finds the package root correctly

Frequently asked questions

What is the difference between textshaping and vcr?

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

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

What are the best alternatives to vcr?

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