webchem
Adding chemical databases with one hand while public ones close programmatic access with the other.
A side-by-side editorial comparison of marquee and mirai — release velocity, themes, recent moves, and the top alternatives to consider.
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.
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.
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.
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.
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.
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.
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.
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.
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 mirai.
Adding chemical databases with one hand while public ones close programmatic access with the other.
The spatiotemporal companion to sf, moving at the pace of the packages around it.
An interface to Europe's long-term ecosystem research network that went quiet after 2.0.
Spatial model assessment that spent the last year on cross-platform arithmetic and CRAN rules.
Stopped trusting the cloud to prepare its taxonomic databases and does the conversion locally.
Went from estimating felling dates to doing the crossdating that produces them.
See all marquee alternatives → · See all mirai alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
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.
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.
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.
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.