← Back to home
Comparison · Analytics

fabletools vs nanonext

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

fabletools vs nanonext: at a glance

Featurefabletoolsnanonext
SectorAnalyticsAnalytics
Velocity score0.02.5
Sparks · 30d00
Top themesforecasting, tidyverts, model-combination, reconciliationasync-messaging, nng, http-server, memory-safety
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 nanonext?

nanonext keeps shrinking its build requirements while adding messaging primitives.

The R binding to NNG ships roughly monthly. Since February the package added an HTTP server that can run synchronously or through the later event loop, a zero-copy device forwarder for building brokers and proxies, and support for pthread-enabled WebAssembly targets. Send operations now move the buffer straight into the NNG message, halving peak memory on serialized sends.

Read the full nanonext trajectory →

fabletools vs nanonext: 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.

N
nanonext
ANALYTICS
2.5

nanonext keeps shrinking its build requirements while adding messaging primitives.

◆ Current state

The R binding to NNG ships roughly monthly. Since February the package added an HTTP server that can run synchronously or through the later event loop, a zero-copy device forwarder for building brokers and proxies, and support for pthread-enabled WebAssembly targets. Send operations now move the buffer straight into the NNG message, halving peak memory on serialized sends.

◆ Where it's heading

Two directions run in parallel. One is making the package installable anywhere — the build-time cmake dependency is gone, so compiling bundled NNG and Mbed TLS needs only a C compiler, and WebAssembly targets are supported. The other is raising the ceiling on what can be built on top: device_aio() for message forwarding, an HTTP and WebSocket server with a content map, and stream buffer control. Bug fixes in recent releases concentrate on memory safety in the bundled C sources.

◆ Prediction

Given the pace and the tight coupling declared in each release, expect the next version to track a mirai requirement and continue hardening the HTTP server paths that the last two releases have been leaking memory in.

Alternatives to fabletools and nanonext

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

See all fabletools alternatives → · See all nanonext alternatives →

Recent activity from fabletools and nanonext

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

  1. 10d agonanonextMemory leaks and a TLS use-after-free fixed in the HTTP server
  2. 1mo agonanonextEvent-loop integration for HTTP and WebSocket callbacks
  3. 1mo agonanonextZero-copy message forwarding, and cmake dropped from the build
  4. 1mo agofabletoolsModel combination rebuilt on joint N-way convolution
  5. 2mo agonanonextBuilds against pthread-enabled WebAssembly targets
  6. 3mo agonanonextSerialized sends drop a copy and halve peak memory
  7. 3mo agofabletoolsCoherency matrices exposed, mdl_lst gains tidier methods
  8. 4mo agonanonextBlocking HTTP server mode and stream buffer sizing
  9. 5mo agofabletoolsGraphics methods now require fabletools to be attached
  10. 6mo agofabletoolsTime series graphics migrating out to ggtime
  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 nanonext?

They serve adjacent needs but don't currently overlap on shipped themes. nanonext 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 nanonext?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. nanonext 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 nanonext?

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