← Back to home
Comparison · Analytics

chattr vs textshaping

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

chattr vs textshaping: at a glance

Featurechattrtextshaping
SectorAnalyticsAnalytics
Velocity score0.00.0
Sparks · 30d00
Top themesllm, rstudio, ide-integration, ellmertypography, text-shaping, bidi, graphics-stack
Last editorial update1h ago4h ago
WebsiteVisit →Visit →

What is chattr?

chattr deleted every LLM integration it had written and outsourced the lot to ellmer

chattr puts a large language model inside the RStudio IDE, either through a Shiny app or directly at the console. As of 0.3.0 it no longer talks to any model provider itself: all integration goes through ellmer, and the hand-written OpenAI, Databricks and LlamaGPT backends were removed. The package's supported model list is now whatever ellmer supports, and the Shiny app streams responses through ellmer rather than managing a background process.

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

chattr vs textshaping: editorial side-by-side

C
chattr
ANALYTICS
0.0

chattr deleted every LLM integration it had written and outsourced the lot to ellmer

◆ Current state

chattr puts a large language model inside the RStudio IDE, either through a Shiny app or directly at the console. As of 0.3.0 it no longer talks to any model provider itself: all integration goes through ellmer, and the hand-written OpenAI, Databricks and LlamaGPT backends were removed. The package's supported model list is now whatever ellmer supports, and the Shiny app streams responses through ellmer rather than managing a background process.

◆ Where it's heading

The first two releases show why that happened. Each provider brought its own error formats, token discovery and response handling, and 0.2.0 is largely a list of per-provider repairs — OpenAI error parsing, Copilot token discovery and model defaults, a new Databricks foundation model backend. Maintaining that surface scales linearly with the number of providers, and the pivot to ellmer trades it for a single dependency. The cost shows up immediately in 0.3.1, which exists solely to absorb a change in ellmer's token object.

◆ Prediction

Expect chattr's releases to now track ellmer's, as 0.3.1 already does, with the package's own work concentrating on the IDE experience rather than model connectivity. New provider support will arrive without a chattr release at all.

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

See all chattr alternatives → · See all textshaping alternatives →

Recent activity from chattr 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. 0y agochattrAdapts to ellmer's token object change
  6. 1y agochattrAll model integration moves to ellmer, direct backends removed
  7. 1y agotextshapingFixes hard line breaks across multiple embeddings
  8. 1y agotextshapingShaping engine rewritten to honour global text direction
  9. 2y agochattrDatabricks foundation models added; per-provider error handling fixed
  10. 2y agochattrFirst release: LLM chat in the RStudio console and app

Frequently asked questions

What is the difference between chattr and textshaping?

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

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

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