← Back to home
Comparison · Analytics

mirai vs webchem

A side-by-side editorial comparison of mirai and webchem — release velocity, themes, recent moves, and the top alternatives to consider.

mirai vs webchem: at a glance

Featuremiraiwebchem
SectorAnalyticsAnalytics
Velocity score2.50.0
Sparks · 30d00
Top themesparallel-computing, async, backpressure, shinycheminformatics, web-apis, data-access, ropensci
Last editorial update3h ago1h ago
WebsiteVisit →Visit →

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.

Read the full mirai trajectory →

What is webchem?

Adding chemical databases with one hand while public ones close programmatic access with the other.

webchem is the R interface to public chemical data — retrieving identifiers, properties and structures across roughly a dozen web services. Its release history reads as a running account of which of those services still allow automated access. Version 1.3.0 removed two functions outright because their sources withdrew: ChemIDplus was retired by the NLM, and PAN stopped supporting programmatic access. Version 1.3.1 continues the pattern, updating URLs that stopped working and noting that ChemSpider InChIKey validation now requires an API key like the rest of that provider's endpoints.

Read the full webchem trajectory →

mirai vs webchem: editorial side-by-side

M
mirai
ANALYTICS
2.5

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.

W
webchem
ANALYTICS
0.0

Adding chemical databases with one hand while public ones close programmatic access with the other.

◆ Current state

webchem is the R interface to public chemical data — retrieving identifiers, properties and structures across roughly a dozen web services. Its release history reads as a running account of which of those services still allow automated access. Version 1.3.0 removed two functions outright because their sources withdrew: ChemIDplus was retired by the NLM, and PAN stopped supporting programmatic access. Version 1.3.1 continues the pattern, updating URLs that stopped working and noting that ChemSpider InChIKey validation now requires an API key like the rest of that provider's endpoints.

◆ Where it's heading

Two opposing forces run through these entries. The package keeps widening its coverage — ChEMBL in 1.2.0, LIPID MAPS and SwissLipids identifiers via Wikidata, structure images, Mol export — while the open, unauthenticated end of the chemical web keeps contracting. The other consistent thread is interface harmonisation: successive releases have converged the get_* functions on the same query and from arguments, tibble returns, and CAS reformatting, so the package feels like one interface rather than a dozen wrappers.

◆ Prediction

Expect further defunct functions and URL repairs as more providers move behind keys or shut down, alongside occasional additions of sources that remain open. The entries show no sign of a general credential-management layer, which is what a package facing this trend would eventually need.

Alternatives to mirai and webchem

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 mirai or webchem.

See all mirai alternatives → · See all webchem alternatives →

Recent activity from mirai and webchem

Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.

  1. 25d agomiraiMap collection and daemon lifecycle fixes
  2. 2mo agomiraiAgent skill ships in-package; HTTP headers take over auth
  3. 3mo agomiraiDispatcher becomes a thread, and the queue gains a memory budget
  4. 5mo agomiraiParallel RNG seeding leaves experimental status
  5. 6mo agomiraiRemote daemons over HTTP, and a C dispatcher loop
  6. 8mo agomiraiTelemetry span timing and daemon-switch fix
  7. 1y agowebchemRepairs broken URLs; ChemSpider check now needs a key
  8. 3y agowebchemChemIDplus and PAN queries removed as sources shut down
  9. 3y agowebchemAdds ChEMBL access for bioactive compound data
  10. 4y agowebchemcir_query() returns a tibble, a breaking change
  11. 4y agowebchemAdds Mol structure export; aw_query renamed to bcpc_query
  12. 5y agowebchemFetches LIPID MAPS and SwissLipids identifiers from Wikidata

Frequently asked questions

What is the difference between mirai and webchem?

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 mirai better than webchem?

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 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.

What are the best alternatives to webchem?

Top webchem alternatives in Analytics are ranked by recent ship velocity. Browse the "webchem alternatives" section above for the current picks, or visit /alternatives/webchem for the full list with editorial commentary on each.