metatools
SDTM supplemental-qualifier merging got sturdier, then the package went quiet for two years.
Comparison · Analytics
goshawk vs mirai
A side-by-side editorial comparison of goshawk and mirai — release velocity, themes, recent moves, and the top alternatives to consider.
goshawk vs mirai: at a glance
What is goshawk?
goshawk's release feed is version-bump automation, not product news.
The three most recent tagged releases are all continuous-integration artefacts: a version bump from 0.1.13.9012 to 0.1.14, an action-skipping bump to 0.1.13.9007, and a date-correction commit. None carries a changelog, and the feed has produced nothing since October 2022.
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.
goshawk vs mirai: editorial side-by-side
goshawk
0.0ANALYTICS
goshawk's release feed is version-bump automation, not product news.
◆ Current state
The three most recent tagged releases are all continuous-integration artefacts: a version bump from 0.1.13.9012 to 0.1.14, an action-skipping bump to 0.1.13.9007, and a date-correction commit. None carries a changelog, and the feed has produced nothing since October 2022.
◆ Where it's heading
The tags follow the insightsengineering release automation — date-stamped names, [skip vbump] and [skip actions] markers, co-author trailers — which means the substance of any release lives in the package's NEWS file rather than here. On the evidence in this feed the repository is dormant.
◆ Prediction
Nothing in these entries supports a prediction about the package's direction; a meaningful signal would need a release that carries actual notes.
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 goshawk 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 goshawk or mirai.
marquee
marquee is filling in the typographic details — outlines, border types, real font metrics for underlines.
logrx
A clinical-script logger that stopped shipping after its 0.2 line, changelogs made of merged PRs.
lobstr
R's object inspector is losing its view of the internals as CRAN closes off the private C API.
GSODR
A weather-station data client that broke one return type to hand back distances instead of bare IDs.
giscoR
giscoR's 1.0 moved its dataset index into the cache, so new Eurostat releases arrive without a package update.
See all goshawk alternatives → · See all mirai alternatives →
Recent activity from goshawk 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
- 3y agogoshawk2022_10_13
- 4y agogoshawk2022_08_16
- 4y agogoshawk2022_06_09: [skip vbump] (#156)
Frequently asked questions
What is the difference between goshawk and mirai?
They serve adjacent needs but don't currently overlap on shipped themes. 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 goshawk 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 goshawk?
Top goshawk alternatives in Analytics are ranked by recent ship velocity. Browse the "goshawk alternatives" section above for the current picks, or visit /alternatives/goshawk 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.