tidytlg
A tables-listings-graphs package that reached CRAN and then went quiet.
Comparison · Analytics
marquee vs webmockr
A side-by-side editorial comparison of marquee and webmockr — release velocity, themes, recent moves, and the top alternatives to consider.
marquee vs webmockr: at a glance
What is marquee?
marquee is filling in the typographic details — outlines, border types, real font metrics for underlines.
marquee renders markdown text onto R graphics devices, and backs element_marquee() and geom_marquee() in ggplot2. Development ran in a tight burst through August and September 2025: 1.1.0 added text outlines, a size shortcut and remote PNG/JPEG support, 1.2.0 added border and outline line types and moved underline placement onto font metrics, and 1.2.1 cleaned up the bugs those introduced.
What is webmockr?
The stubbing library added httr2 support, then spent a year cutting itself free of everything else
webmockr intercepts HTTP requests in R tests and returns stubbed responses, and since 1.0.0 it covers all three clients that matter — httr, httr2 and crul. The releases through 2025 have been about shedding dependencies: internal R6 classes unexported in 2.1.0, crul demoted from Imports to Suggests in the same release, and the mutual dependency with vcr severed in 2.2.0. The package now installs and runs without pulling in the rest of the rOpenSci HTTP stack.
marquee vs webmockr: editorial side-by-side
marquee
0.0ANALYTICS
marquee is filling in the typographic details — outlines, border types, real font metrics for underlines.
◆ Current state
marquee renders markdown text onto R graphics devices, and backs element_marquee() and geom_marquee() in ggplot2. Development ran in a tight burst through August and September 2025: 1.1.0 added text outlines, a size shortcut and remote PNG/JPEG support, 1.2.0 added border and outline line types and moved underline placement onto font metrics, and 1.2.1 cleaned up the bugs those introduced.
◆ Where it's heading
The package is converging on typographic fidelity rather than new capability. Early work settled layout semantics — CSS margin collapsing, inline padding reserving space during shaping, devices without glyph support — and recent releases refine how decorations are drawn and measured. The naming cleanup in 1.2.0, border_size becoming border_width, reads as an API being tidied ahead of wider use rather than one still being explored.
◆ Prediction
Expect continued small releases sanding down rendering edge cases in ggplot2 contexts, since that is where the recent bug reports come from; nothing here signals a new feature area.
webmockr
0.0ANALYTICS
The stubbing library added httr2 support, then spent a year cutting itself free of everything else
◆ Current state
webmockr intercepts HTTP requests in R tests and returns stubbed responses, and since 1.0.0 it covers all three clients that matter — httr, httr2 and crul. The releases through 2025 have been about shedding dependencies: internal R6 classes unexported in 2.1.0, crul demoted from Imports to Suggests in the same release, and the mutual dependency with vcr severed in 2.2.0. The package now installs and runs without pulling in the rest of the rOpenSci HTTP stack.
◆ Where it's heading
Two arcs run in sequence. The first is coverage — multiple queued responses in 0.7.0, basic auth mocking, async through crul, then httr2 — building out what can be stubbed. The second, starting with 2.0.0, is correctness and independence: stubs are now deleted if an error occurs mid-construction rather than lingering half-built, partial matching arrives for bodies and queries, and the dependency graph is pruned release by release. The 2.2.0 split from vcr landed within a minute of crul's release taking mocking control into its own clients.
◆ Prediction
RequestPattern is documented as still exported in 2.1.0 but slated for removal, so the next major release is where that lands. Expect continued dependency pruning rather than new client support — the three clients that exist are already covered.
Alternatives to marquee and webmockr
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 marquee or webmockr.
Tplyr
Tplyr made clinical summary tables explain where every number came from.
rlistings
Clinical listings that keep inheriting their hardest problem — pagination — from the layer below.
hoardr
A cache-directory helper that has shipped nothing but CRAN-triggered patches for seven years.
gigs
gigs redesigned its whole conversion API for rOpenSci, then spent three releases getting the docs to build.
riem
A weather-data client that keeps rewriting its HTTP layer while slowly tightening its API.
See all marquee alternatives → · See all webmockr alternatives →
Recent activity from marquee and webmockr
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 11mo agomarqueeBug fixes for relative sizes, outlines and guide width
- 11mo agomarqueeBorder and outline line types; underlines follow font metrics
- 11mo agomarqueeRotated text width fixed; factor input supported
- 0y agomarqueeText outlines, size shortcuts and images from URLs
- 1y agowebmockrvcr dependency severed
- 1y agowebmockrInternal classes unexported; crul becomes an optional dependency
- 1y agowebmockrFailed stub construction cleans up; partial matching extends to bodies and queries
- 1y agomarquee1.0 settles margin collapsing and inline decoration spacing
- 2y agowebmockrhttr2 joins httr and crul as a supported client ⚡
- 3y agowebmockrQueued responses, body matching and integer status codes fixed
- 3y agowebmockrRegex URI matching fixed
Frequently asked questions
What is the difference between marquee and webmockr?
They serve adjacent needs but don't currently overlap on shipped themes. marquee and webmockr 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 marquee better than webmockr?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. marquee and webmockr 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 marquee?
Top marquee alternatives in Analytics are ranked by recent ship velocity. Browse the "marquee alternatives" section above for the current picks, or visit /alternatives/marquee for the full list with editorial commentary on each.
What are the best alternatives to webmockr?
Top webmockr alternatives in Analytics are ranked by recent ship velocity. Browse the "webmockr alternatives" section above for the current picks, or visit /alternatives/webmockr for the full list with editorial commentary on each.