← Back to home
Comparison · Analytics

fabletools vs nanoparquet

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

fabletools vs nanoparquet: at a glance

Featurefabletoolsnanoparquet
SectorAnalyticsAnalytics
Velocity score0.00.0
Sparks · 30d00
Top themesforecasting, tidyverts, model-combination, reconciliationparquet, r-language, interoperability, data-formats
Last editorial update1h ago45m 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 nanoparquet?

nanoparquet is chasing byte-level agreement with the Java and Rust Parquet readers, not feature count.

nanoparquet reads and writes Parquet from R with no Arrow dependency, which is its entire reason to exist. The 0.4.0 line renamed the reader API and added schema authoring plus `append_parquet()`, and the 0.5.x releases have gone after interoperability: definition and repetition level encodings the Apache Parquet Java library expects, flatbuffer alignment the Rust arrow-rs reader expects, 128-bit decimals, and Polars-written files that omit the dictionary page offset. The newest release adds `bit64::integer64` columns and writing to stdout.

Read the full nanoparquet trajectory →

fabletools vs nanoparquet: 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
nanoparquet
ANALYTICS
0.0

nanoparquet is chasing byte-level agreement with the Java and Rust Parquet readers, not feature count.

◆ Current state

nanoparquet reads and writes Parquet from R with no Arrow dependency, which is its entire reason to exist. The 0.4.0 line renamed the reader API and added schema authoring plus `append_parquet()`, and the 0.5.x releases have gone after interoperability: definition and repetition level encodings the Apache Parquet Java library expects, flatbuffer alignment the Rust arrow-rs reader expects, 128-bit decimals, and Polars-written files that omit the dictionary page offset. The newest release adds `bit64::integer64` columns and writing to stdout.

◆ Where it's heading

Almost every entry since 0.4.0 names another engine — Java, arrow-rs, Polars, Arrow schema metadata — which tells you the maintainers are treating cross-reader fidelity as the product rather than R-side ergonomics. The type system is filling in from the edges: DECIMAL beyond 8 bytes, UUID, FLOAT16 and INTERVAL as raw lists, and now 64-bit integers with an explicit read-type option instead of a silent cast to double. Writing to `:stdout:` points at a second audience, shell pipelines rather than interactive R.

◆ Prediction

The remaining unmapped Parquet types the changelog has been parking in raw-vector lists — FLOAT16 and INTERVAL — are the obvious next targets, following the same pattern by which DECIMAL and UUID graduated to real R types.

Alternatives to fabletools and nanoparquet

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

See all fabletools alternatives → · See all nanoparquet alternatives →

Recent activity from fabletools and nanoparquet

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

  1. 1mo agofabletoolsModel combination rebuilt on joint N-way convolution
  2. 3mo agofabletoolsCoherency matrices exposed, mdl_lst gains tidier methods
  3. 3mo agonanoparquet64-bit integer columns and writing Parquet to stdout
  4. 4mo agonanoparquetFiles now readable by the Java and Rust Parquet libraries
  5. 5mo agofabletoolsGraphics methods now require fabletools to be attached
  6. 6mo agofabletoolsTime series graphics migrating out to ggtime
  7. 8mo agofabletoolsggplot2 4.0.0 compatibility patch
  8. 8mo agofabletoolsIRF() generic and multivariate bootstrap sample paths
  9. 1y agonanoparquetReads Polars files that omit the dictionary page offset
  10. 1y agonanoparquetDate, FLOAT, and mixed-encoding read fixes
  11. 1y agonanoparquetSchema authoring and append_parquet arrive with a renamed API
  12. 1y agonanoparquetFixes a write_parquet crash

Frequently asked questions

What is the difference between fabletools and nanoparquet?

They serve adjacent needs but don't currently overlap on shipped themes. fabletools and nanoparquet are shipping at a similar cadence (velocity 0.0 vs 0.0, both within Sparkpulse's "active" band). See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.

Is fabletools better than nanoparquet?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. fabletools and nanoparquet are shipping at a similar cadence (velocity 0.0 vs 0.0, both within Sparkpulse's "active" band). 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 nanoparquet?

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