datefixR
The messy-date parser rewrote its core in Rust and came out 300x faster.
Comparison · Analytics
patentsview vs textshaping
A side-by-side editorial comparison of patentsview and textshaping — release velocity, themes, recent moves, and the top alternatives to consider.
Shared themes:r-package
patentsview vs textshaping: at a glance
What is patentsview?
Dormant for years, then rewritten wholesale when the API underneath it broke.
patentsview is an R client for the USPTO PatentsView API, and version 1.0.0 is less a feature release than a forced reconstruction: the upstream API introduced mandatory keys, renamed and re-nested its endpoints, and the package had to follow. Between 2017 and 2021 the release cadence was roughly annual and almost entirely defensive — wrapping examples so CRAN would not fail during API outages, patching URL encoding, adding throttling retries. The 1.0.0 work restores the package to parity with an API that no longer resembles the one it was written against.
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.
patentsview vs textshaping: editorial side-by-side
patentsview
0.0ANALYTICS
Dormant for years, then rewritten wholesale when the API underneath it broke.
◆ Current state
patentsview is an R client for the USPTO PatentsView API, and version 1.0.0 is less a feature release than a forced reconstruction: the upstream API introduced mandatory keys, renamed and re-nested its endpoints, and the package had to follow. Between 2017 and 2021 the release cadence was roughly annual and almost entirely defensive — wrapping examples so CRAN would not fail during API outages, patching URL encoding, adding throttling retries. The 1.0.0 work restores the package to parity with an API that no longer resembles the one it was written against.
◆ Where it's heading
The arc here is a client package whose roadmap is entirely dictated by an upstream service it does not control. Every release since 0.2.0 has been reactive — HTTPS migration, throttling, encoding fixes, and now a full breaking rewrite. The one forward-looking piece is retrieve_linked_data(), which follows HATEOAS links the API now returns, meaning the package is starting to navigate the API rather than just query fixed endpoints.
◆ Prediction
Expect the next releases to be small follow-ups against the reworked API — field list refreshes and error handling for endpoints that behave differently in practice than in the documentation. The entries do not show any independent roadmap, so anything beyond that would depend on further upstream API changes.
textshaping
0.0ANALYTICS
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 patentsview 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 patentsview or textshaping.
maplegend
The legend engine mapsf spun out, now covering legend types the parent map package can draw.
lang
R help pages translated on demand by whichever LLM you point it at.
mapsf
Thematic mapping in base R that finally got a theming system, then spent two years polishing legends.
qualtRics
qualtRics moved its contact functions onto XM Directory days before the old endpoints died.
fabletools
The tidyverts forecasting core rebuilt model combination on full residual covariance.
See all patentsview alternatives → · See all textshaping alternatives →
Recent activity from patentsview and textshaping
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 5mo agotextshapingFixes reverting between font fallbacks
- 6mo agopatentsviewRebuilt for PatentsView's new API: keys, nested endpoints ⚡
- 9mo agotextshapingGuards against freetype version mismatches with systemfonts
- 11mo agotextshapingFixes a signed integer overflow in the previous fix
- 11mo agotextshapingFixes bidi single-line shaping and a weak shape-cache hash
- 1y agotextshapingFixes hard line breaks across multiple embeddings
- 1y agotextshapingShaping engine rewritten to honour global text direction ⚡
- 4y agopatentsviewMoves to HTTPS endpoints and handles API throttling
- 7y agopatentsviewVignettes dropped so CRAN builds survive API outages
- 8y agopatentsviewAPI examples wrapped in dontrun for CRAN stability
- 8y agopatentsviewcast_pv_data() converts returned columns to real types
- 9y agopatentsviewFirst release: query DSL for the PatentsView API
Frequently asked questions
What is the difference between patentsview and textshaping?
Both compete on the same themes — r-package — within Analytics. patentsview 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 patentsview better than textshaping?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. patentsview 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 patentsview?
Top patentsview alternatives in Analytics are ranked by recent ship velocity. Browse the "patentsview alternatives" section above for the current picks, or visit /alternatives/patentsview 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.