tidytlg
A tables-listings-graphs package that reached CRAN and then went quiet.
Comparison · Analytics
crul vs mirai
A side-by-side editorial comparison of crul and mirai — release velocity, themes, recent moves, and the top alternatives to consider.
Shared themes:async
crul vs mirai: at a glance
What is crul?
crul took mocking back from webmockr and made it a property of the client itself
crul is the R6-based HTTP client underneath much of rOpenSci's package stack, covering synchronous requests, three flavours of async, pagination and retries. Its 1.6.0 release in July 2025 changed where test mocking lives: each client — HttpClient, Async, AsyncVaried — now takes a mocking parameter at initialisation or per method, and the standalone mock() function is deprecated. Mocking used to be something webmockr switched on from outside; it is now a setting on the client.
What is mirai?
mirai removed its dispatcher process and added memory backpressure to the queue.
The async evaluation framework releases roughly monthly and moves fast at the architecture level. In 2.7.0 the dispatcher stopped being a separate process and became a thread, after its loop had already been rewritten in C inside nanonext one release earlier. The same release added an opt-in memory budget for queued task payloads and try_mirai(), which returns NULL immediately rather than blocking when that budget is exhausted.
crul vs mirai: editorial side-by-side
crul
0.0ANALYTICS
crul took mocking back from webmockr and made it a property of the client itself
◆ Current state
crul is the R6-based HTTP client underneath much of rOpenSci's package stack, covering synchronous requests, three flavours of async, pagination and retries. Its 1.6.0 release in July 2025 changed where test mocking lives: each client — HttpClient, Async, AsyncVaried — now takes a mocking parameter at initialisation or per method, and the standalone mock() function is deprecated. Mocking used to be something webmockr switched on from outside; it is now a setting on the client.
◆ Where it's heading
The async surface has been the growth area for years — retries reached Async, AsyncVaried, AsyncQueue and HttpRequest in 1.4, AsyncQueue gained the response accessors in 1.2, and 1.5.0 wired async requests up to webmockr. The 1.6.0 change reverses that direction of dependency, and it landed within a minute of webmockr's own release severing its tie to vcr. Read together, the rOpenSci HTTP stack is being deliberately untangled so each package can be used without the others.
◆ Prediction
With mock() deprecated rather than removed, the next major release is the likely point of deletion. Expect the remaining work to follow the same decoupling theme rather than adding request features.
mirai
2.5ANALYTICS
mirai removed its dispatcher process and added memory backpressure to the queue.
◆ Current state
The async evaluation framework releases roughly monthly and moves fast at the architecture level. In 2.7.0 the dispatcher stopped being a separate process and became a thread, after its loop had already been rewritten in C inside nanonext one release earlier. The same release added an opt-in memory budget for queued task payloads and try_mirai(), which returns NULL immediately rather than blocking when that budget is exhausted.
◆ Where it's heading
Two threads of work run together: cutting overhead out of the task path — thread-based dispatcher, in-process transport for synchronous daemons, lower per-element dispatch cost in mirai_map() — and making the framework safe to embed in an event loop, where blocking the host R thread is not acceptable. Deployment reach is growing too, with http_config() launching remote daemons over HTTP APIs and auto-configuring for Posit Workbench. Each release pins a minimum nanonext version, so the two packages advance as one unit.
◆ Prediction
With backpressure in place but opt-in, the open question these notes leave is whether a default memory budget arrives; continued overhead reduction and Shiny-facing non-blocking paths are the safer bet.
Alternatives to crul and mirai
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 crul or mirai.
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.
Recent activity from crul and mirai
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 25d agomiraiMap collection and daemon lifecycle fixes
- 2mo agomiraiAgent skill ships in-package; HTTP headers take over auth
- 3mo agomiraiDispatcher becomes a thread, and the queue gains a memory budget ⚡
- 5mo agomiraiParallel RNG seeding leaves experimental status
- 6mo agomiraiRemote daemons over HTTP, and a C dispatcher loop
- 8mo agomiraiTelemetry span timing and daemon-switch fix
- 1y agocrulMocking becomes a client parameter, independent of webmockr ⚡
- 2y agocrulAsync requests become mockable through webmockr
- 2y agocrulDocumentation fixes and test helper tweak
- 3y agocrulHTTP retries reach the async classes
- 3y agocrulClearer error for mismatched urls and disk lengths
- 4y agocrulAsyncQueue gains response accessors; results print as a summary
Frequently asked questions
What is the difference between crul and mirai?
Both compete on the same themes — async — within Analytics. mirai is currently shipping more aggressively (velocity 2.5 vs 0.0), with 0 editorial sparks in the last 30 days against 0. See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.
Is crul better than mirai?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. mirai is currently shipping more aggressively (velocity 2.5 vs 0.0), with 0 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other Analytics products to evaluate alongside.
What are the best alternatives to crul?
Top crul alternatives in Analytics are ranked by recent ship velocity. Browse the "crul alternatives" section above for the current picks, or visit /alternatives/crul for the full list with editorial commentary on each.
What are the best alternatives to mirai?
Top mirai alternatives in Analytics are ranked by recent ship velocity. Browse the "mirai alternatives" section above for the current picks, or visit /alternatives/mirai for the full list with editorial commentary on each.