← Back to home
Comparison · Infra & APIs

FoReco vs frontmatter

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

Shared themes:r-package

FoReco vs frontmatter: at a glance

FeatureFoRecofrontmatter
SectorInfra & APIsInfra & APIs
Velocity score0.00.0
Sparks · 30d00
Top themesforecasting, hierarchical-reconciliation, time-series, s3-classesparsing, yaml, toml, r-package
Last editorial update53m ago2d ago
WebsiteVisit →Visit →

What is FoReco?

Forecast reconciliation with a real object model, five years after it started returning bare matrices.

FoReco reconciles hierarchical forecasts across cross-sectional, temporal, and cross-temporal frameworks, and now covers both point and probabilistic reconciliation. The 1.3.0 release gave every reconciliation function a shared foreco S3 class carrying framework, function, forecast type, and reconciliation metadata, which replaced the loose attribute-and-helper pattern the package had used since 1.0.0. The follow-up 1.3.1 turned the same attention on the API's edges: strict argument validation with errors that name the expected and supplied values, and a help index pruned down to user-facing functions only.

Read the full FoReco trajectory →

What is frontmatter?

A small R parser quietly becoming format-agnostic about front matter.

frontmatter extracts and writes YAML or TOML front matter from text documents, with a C++ parser and pluggable YAML and TOML backends. Three releases across six months have taken it from read-only parsing to full roundtrip and then to inferring format automatically. Its scope is deliberately narrow: locating and delimiting the metadata block, and delegating the actual parsing to other packages.

Read the full frontmatter trajectory →

FoReco vs frontmatter: editorial side-by-side

F
FoReco
INFRA · APIS
0.0

Forecast reconciliation with a real object model, five years after it started returning bare matrices.

◆ Current state

FoReco reconciles hierarchical forecasts across cross-sectional, temporal, and cross-temporal frameworks, and now covers both point and probabilistic reconciliation. The 1.3.0 release gave every reconciliation function a shared foreco S3 class carrying framework, function, forecast type, and reconciliation metadata, which replaced the loose attribute-and-helper pattern the package had used since 1.0.0. The follow-up 1.3.1 turned the same attention on the API's edges: strict argument validation with errors that name the expected and supplied values, and a help index pruned down to user-facing functions only.

◆ Where it's heading

The package is completing a reversal it started in 1.0.0. That release simplified outputs to plain matrices and pushed metadata into attributes reachable via recoinfo(); 1.3.0 removed recoinfo() outright and put the structure back as a class with components(), summary(), and plot() methods. The direction is toward being infrastructure rather than a function library — the class is exported through new_foreco_class() and a sibling package has already adopted it. Method coverage has meanwhile broadened from optimal combination into non-negative algorithms, bounded reconciliation, and Gaussian and sample-based probabilistic variants.

◆ Prediction

The soft-deprecated res2matrix() is flagged for removal, so a subsequent release should finish that cleanup; with the class now exported, expect more methods to hang off foreco objects rather than more top-level functions.

F
frontmatter
INFRA · APIS
0.0

A small R parser quietly becoming format-agnostic about front matter.

◆ Current state

frontmatter extracts and writes YAML or TOML front matter from text documents, with a C++ parser and pluggable YAML and TOML backends. Three releases across six months have taken it from read-only parsing to full roundtrip and then to inferring format automatically. Its scope is deliberately narrow: locating and delimiting the metadata block, and delegating the actual parsing to other packages.

◆ Where it's heading

Each release widens the set of files it recognises without widening what it claims to do — standard YAML and TOML fences first, then comment-wrapped R and Python variants and PEP 723 inline script metadata, then shebang-prefixed scripts. The complementary thread is preserving what it found: format and fence type are attached as attributes so a document can be rewritten in the style it arrived in. The remaining rough edge is acknowledged in the notes, since comments and formatting inside the front matter do not survive a roundtrip.

◆ Prediction

Expect further delimiter styles as they appear in the wild, and likely work on making the roundtrip preserve comments and formatting, which the package currently flags as imperfect.

Alternatives to FoReco and frontmatter

Other Infra & APIs 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 FoReco or frontmatter.

See all FoReco alternatives → · See all frontmatter alternatives →

Recent activity from FoReco and frontmatter

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

  1. 1mo agoFoRecoStrict argument validation and a pruned help index
  2. 1mo agofrontmatterDelimiter inferred automatically, and shebang lines supported
  3. 1mo agoFoRecoEvery reconciliation function now returns a shared foreco object
  4. 3mo agoFoRecoBootstrap functions gain xreg; simulate() argument bug fixed
  5. 5mo agoFoRecoGaussian and sample-based probabilistic reconciliation added
  6. 6mo agofrontmatterWriting support completes the parse-and-rewrite roundtrip
  7. 7mo agofrontmatterFirst release: multi-format front matter parsing in C++
  8. 1y agoFoRecoBounded reconciliation and an oracle shrunk covariance estimator
  9. 1y agoFoRecoBreaking rename: cs, te and ct prefixes across all functions

Frequently asked questions

What is the difference between FoReco and frontmatter?

Both compete on the same themes — r-package — within Infra & APIs. FoReco and frontmatter 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 FoReco better than frontmatter?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. FoReco and frontmatter 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 Infra & APIs products to evaluate alongside.

What are the best alternatives to FoReco?

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

What are the best alternatives to frontmatter?

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