← Back to home
Comparison · Analytics

fabletools vs mirai

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

fabletools vs mirai: at a glance

Featurefabletoolsmirai
SectorAnalyticsAnalytics
Velocity score0.02.5
Sparks · 30d00
Top themesforecasting, tidyverts, model-combination, reconciliationparallel-computing, async, backpressure, shiny
Last editorial update54m ago3h ago
WebsiteVisit →Visit →

What is fabletools?

The tidyverts forecasting core rebuilt model combination on full residual covariance.

fabletools is the framework layer under fable and fpp3 — mables, fables, accuracy measures, reconciliation, and the model arithmetic that lets forecasters express ensembles as expressions. Version 0.8.0 reworked that arithmetic: combination now uses a joint N-way convolution accounting for the full residual covariance across components rather than composing pairwise, and every arithmetic operator collapses to a single model_combination with correctly implied weights, so nested expressions like ((m1 + m2)/2 + m3)/2 flatten automatically. In parallel, the package has been shedding graphics to {ggtime} on a deliberately slow deprecation clock.

Read the full fabletools trajectory →

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 →

fabletools vs mirai: editorial side-by-side

F
fabletools
ANALYTICS
0.0

The tidyverts forecasting core rebuilt model combination on full residual covariance.

◆ Current state

fabletools is the framework layer under fable and fpp3 — mables, fables, accuracy measures, reconciliation, and the model arithmetic that lets forecasters express ensembles as expressions. Version 0.8.0 reworked that arithmetic: combination now uses a joint N-way convolution accounting for the full residual covariance across components rather than composing pairwise, and every arithmetic operator collapses to a single model_combination with correctly implied weights, so nested expressions like ((m1 + m2)/2 + m3)/2 flatten automatically. In parallel, the package has been shedding graphics to {ggtime} on a deliberately slow deprecation clock.

◆ Where it's heading

The framework is being narrowed and deepened at the same time. Narrowed, because plotting is moving out to a dedicated package over an announced two-year deprecation, leaving fabletools to modeling infrastructure. Deepened, because the recent statistical work targets correctness in places users could not easily inspect — combination weights, inverse-variance weighting computed on response rather than innovation residuals, reconciliation coherency matrices exposed via coherent_smat() and coherent_cmat(). Class hygiene follows the same instinct, with mdl_lst replacing lst_mdl and gaining augment(), glance(), and tidy() so global and reconciliation models report statistics like any other.

◆ Prediction

With combination and reconciliation infrastructure freshly reworked, the remaining announced work is the ggtime separation, so expect the graphics re-exports to keep degrading toward removal while modeling changes stay incremental.

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.

Alternatives to fabletools 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 fabletools or mirai.

See all fabletools alternatives → · See all mirai alternatives →

Recent activity from fabletools and mirai

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

  1. 25d agomiraiMap collection and daemon lifecycle fixes
  2. 1mo agofabletoolsModel combination rebuilt on joint N-way convolution
  3. 2mo agomiraiAgent skill ships in-package; HTTP headers take over auth
  4. 3mo agomiraiDispatcher becomes a thread, and the queue gains a memory budget
  5. 3mo agofabletoolsCoherency matrices exposed, mdl_lst gains tidier methods
  6. 5mo agomiraiParallel RNG seeding leaves experimental status
  7. 5mo agofabletoolsGraphics methods now require fabletools to be attached
  8. 6mo agomiraiRemote daemons over HTTP, and a C dispatcher loop
  9. 6mo agofabletoolsTime series graphics migrating out to ggtime
  10. 8mo agomiraiTelemetry span timing and daemon-switch fix
  11. 8mo agofabletoolsggplot2 4.0.0 compatibility patch
  12. 8mo agofabletoolsIRF() generic and multivariate bootstrap sample paths

Frequently asked questions

What is the difference between fabletools 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 fabletools 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 fabletools?

Top fabletools alternatives in Analytics are ranked by recent ship velocity. Browse the "fabletools alternatives" section above for the current picks, or visit /alternatives/fabletools 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.