WPML
WPML made machine translation the default, and its point releases keep chasing WordPress and page builders.
Comparison · Infra & APIs
eratosthenes vs retroharmonize
A side-by-side editorial comparison of eratosthenes and retroharmonize — release velocity, themes, recent moves, and the top alternatives to consider.
Shared themes:r-package
eratosthenes vs retroharmonize: at a glance
What is eratosthenes?
eratosthenes spends 0.1.0 hardening inputs rather than adding chronology methods.
eratosthenes does Bayesian estimation of archaeological chronologies from relative sequences, absolute constraints and artifact assemblages. The 0.0.9 line built out the inference diagnostics — traceplots, histograms, batch-means MCSE reporting, displacement estimation — and then consolidated artifact probability-density estimation into a single gibbs_ad_type(). The 0.1.0 tag turns outward instead, adding validators for every user-supplied structure and replacing seq_check() with a more informative seq_diag().
What is retroharmonize?
Survey harmonization tooling that spent its last release earning its way back onto CRAN.
retroharmonize handles retrospective harmonization of survey microdata — reconciling value codes, value labels, variable names, and missing-value ranges across waves so separate surveys can be joined or panelled reproducibly. The most recent release was not about any of that: the package had been archived from CRAN when a dependency was archived, and the work went into refactoring the labelled_spss_survey vctrs integration, separating core, print, arithmetic, and vctrs methods, and passing checks across five platforms plus R-devel.
eratosthenes vs retroharmonize: editorial side-by-side
eratosthenes
2.5INFRA · APIS
eratosthenes spends 0.1.0 hardening inputs rather than adding chronology methods.
◆ Current state
eratosthenes does Bayesian estimation of archaeological chronologies from relative sequences, absolute constraints and artifact assemblages. The 0.0.9 line built out the inference diagnostics — traceplots, histograms, batch-means MCSE reporting, displacement estimation — and then consolidated artifact probability-density estimation into a single gibbs_ad_type(). The 0.1.0 tag turns outward instead, adding validators for every user-supplied structure and replacing seq_check() with a more informative seq_diag().
◆ Where it's heading
The package is moving from research code to something a non-author can run. Consolidating estimation behind one function, then wrapping every input class in a validator, are the two steps that make failures legible instead of cryptic, and the diagnostics added earlier serve the same end for the sampler itself. Nothing in the window changes the underlying model; the work is all about making it usable and its output checkable.
◆ Prediction
With inputs validated and diagnostics in place, the next release is more likely to extend the constraint or assemblage modelling than to keep reworking the interface, though the feed's three sparse tags give little to read a cadence from.
retroharmonize
0.0INFRA · APIS
Survey harmonization tooling that spent its last release earning its way back onto CRAN.
◆ Current state
retroharmonize handles retrospective harmonization of survey microdata — reconciling value codes, value labels, variable names, and missing-value ranges across waves so separate surveys can be joined or panelled reproducibly. The most recent release was not about any of that: the package had been archived from CRAN when a dependency was archived, and the work went into refactoring the labelled_spss_survey vctrs integration, separating core, print, arithmetic, and vctrs methods, and passing checks across five platforms plus R-devel.
◆ Where it's heading
The design bet has been constant since the first release — comprehensive S3 classes that carry labels and missing-value semantics through every transformation, so the harmonization is documented rather than reconstructed. What has changed is where effort goes. Early releases added harmonization functions and a worked Arab Barometer case study; recent ones are code quality and CRAN survival. Note that the version numbering in this feed is not monotonic: 0.1.13 was released roughly nine months before 0.1.7, so version order here does not indicate release order.
◆ Prediction
Having just restored CRAN availability through a refactor rather than a feature, the near-term work is most likely consolidation of the vctrs integration the notes describe rather than new harmonization functions.
Alternatives to eratosthenes and retroharmonize
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 eratosthenes or retroharmonize.
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 eratosthenes alternatives → · See all retroharmonize alternatives →
Recent activity from eratosthenes and retroharmonize
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 10d agoeratosthenesInput validators added; seq_check() replaced by seq_diag()
- 3mo agoretroharmonizeCRAN modernisation release
- 7mo agoretroharmonizeRelease candidate; notes cite code quality with no detail
- 1y agoeratosthenesArtifact p.d.f. estimation consolidated into gibbs_ad_type()
- 1y agoeratosthenesMCMC diagnostics arrive: traceplots, histograms, batch-means MCSE
- 4y agoretroharmonizeImproved documentation
- 5y agoretroharmonize0.1.7 With case study on harmonizing Arab Barometer surveys
- 5y agoretroharmonizeretroharmonize 0.1.13 is on CRAN
- 6y agoretroharmonize0.1.0 Retrospective harmonization of survey data files in R ⚡
Frequently asked questions
What is the difference between eratosthenes and retroharmonize?
Both compete on the same themes — r-package — within Infra & APIs. eratosthenes 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 eratosthenes better than retroharmonize?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. eratosthenes 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 Infra & APIs products to evaluate alongside.
What are the best alternatives to eratosthenes?
Top eratosthenes alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "eratosthenes alternatives" section above for the current picks, or visit /alternatives/eratosthenes for the full list with editorial commentary on each.
What are the best alternatives to retroharmonize?
Top retroharmonize alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "retroharmonize alternatives" section above for the current picks, or visit /alternatives/retroharmonize for the full list with editorial commentary on each.