WPML
WPML made machine translation the default, and its point releases keep chasing WordPress and page builders.
Comparison · Infra & APIs
FoReco vs survivoR
A side-by-side editorial comparison of FoReco and survivoR — release velocity, themes, recent moves, and the top alternatives to consider.
Shared themes:r-package
FoReco vs survivoR: at a glance
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.
What is survivoR?
A Survivor data package that keeps turning a TV show into a relational database
survivoR ships Survivor franchise data as R data frames covering the US, Australian, UK and New Zealand versions. Recent releases track broadcast: US48, US49 and US50 arrived across 2.3.6, 2.3.9 and 2.3.12, alongside AU09, AU12 and Australia vs. The World. The 2.3.12 release also reworked castaway_scores into an explicit three-tier structure - standardised residual scores, probabilistic scores bounded on [0,1], and combined scores - and added advantage_timeline as a long-format view of advantage movement.
FoReco vs survivoR: editorial side-by-side
FoReco
0.0INFRA · APIS
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.
survivoR
0.0INFRA · APIS
A Survivor data package that keeps turning a TV show into a relational database
◆ Current state
survivoR ships Survivor franchise data as R data frames covering the US, Australian, UK and New Zealand versions. Recent releases track broadcast: US48, US49 and US50 arrived across 2.3.6, 2.3.9 and 2.3.12, alongside AU09, AU12 and Australia vs. The World. The 2.3.12 release also reworked castaway_scores into an explicit three-tier structure - standardised residual scores, probabilistic scores bounded on [0,1], and combined scores - and added advantage_timeline as a long-format view of advantage movement.
◆ Where it's heading
The work is less about adding seasons than about making the tables join cleanly. 2.3.1 rebuilt challenge_description and challenge_results around a shared challenge_id, added challenge characteristic flags and result notes, and put logical finalist, winner and jury flags on castaways. Since then the pattern repeats at smaller scale: boot_order as its own table, season_name deprecated everywhere except season_summary, castaways cleaned so people booted twice appear once. Derived analytical columns are being separated from raw records rather than mixed into them.
◆ Prediction
Expect the next release to add the current season's data on the same broadcast-following cadence, with any structural work continuing to split derived scores out of the raw tables.
Alternatives to FoReco and survivoR
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 survivoR.
forestploter
A forest plot package that keeps handing users control of one more graphical detail.
ggInterval
Interval-valued data plotting, spending 2026 making its function names and examples survive CRAN.
rgm
A microbiome network model that got itself un-archived by deleting the dependency that killed it.
contagionchannels
Three releases in ten days, every one of them a CRAN reviewer's correction rather than a code change.
tidyaudit
Pipeline provenance for tidyverse workflows, recording what changed at each step without keeping the data.
See all FoReco alternatives → · See all survivoR alternatives →
Recent activity from FoReco and survivoR
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 1mo agoFoRecoStrict argument validation and a pruned help index
- 1mo agoFoRecoEvery reconciliation function now returns a shared foreco object ⚡
- 2mo agosurvivoRUS50 and AU12 land, castaway scores split into three tiers
- 3mo agoFoRecoBootstrap functions gain xreg; simulate() argument bug fixed
- 5mo agoFoRecoGaussian and sample-based probabilistic reconciliation added
- 7mo agosurvivoRUS49 data completed and season 50 cast added
- 11mo agosurvivoRSurvivor Australia vs. The World added
- 1y agosurvivoRboot_order table added and castaways deduplicated
- 1y agoFoRecoBounded reconciliation and an oracle shrunk covariance estimator
- 1y agoFoRecoBreaking rename: cs, te and ct prefixes across all functions
- 2y agosurvivoRComplete AU09 data reaches CRAN
- 2y agosurvivoRChallenge tables rebuilt around a shared linking key
Frequently asked questions
What is the difference between FoReco and survivoR?
Both compete on the same themes — r-package — within Infra & APIs. FoReco and survivoR 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 survivoR?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. FoReco and survivoR 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 survivoR?
Top survivoR alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "survivoR alternatives" section above for the current picks, or visit /alternatives/survivor for the full list with editorial commentary on each.