Traefik
Traefik's 2.11 line spends August fixing the names it generates for Kubernetes resources.
Comparison · Infra & APIs
CHNOSZ vs surveycore
A side-by-side editorial comparison of CHNOSZ and surveycore — release velocity, themes, recent moves, and the top alternatives to consider.
CHNOSZ vs surveycore: at a glance
What is CHNOSZ?
A geochemistry thermodynamics engine that changed its units and its database schema in one release.
CHNOSZ computes thermodynamic properties and phase diagrams for geochemical systems, backed by OBIGT, its bundled thermodynamic database. It releases roughly once a year with a short highlights note pointing at a full changelog elsewhere. Since the 2.0.0 reset, work has been curation and communication: new species in OBIGT, a FAQ vignette, a rewritten introduction, and more readable diagram labels.
What is surveycore?
surveycore declared its API stable with every survey design type covered.
surveycore is the estimation engine of a two-package survey stack, handling design objects and variance estimation while surveytidy supplies the dplyr verbs on top. The June release marks it 1.0.0 and states the API is complete and stable across Taylor series linearization, replicate weights, two-phase and non-probability designs, with means, totals, frequencies, quantiles, ratios, correlations, regression, t-tests, ANOVA and effective sample size all in place.
CHNOSZ vs surveycore: editorial side-by-side
CHNOSZ
0.0INFRA · APIS
A geochemistry thermodynamics engine that changed its units and its database schema in one release.
◆ Current state
CHNOSZ computes thermodynamic properties and phase diagrams for geochemical systems, backed by OBIGT, its bundled thermodynamic database. It releases roughly once a year with a short highlights note pointing at a full changelog elsewhere. Since the 2.0.0 reset, work has been curation and communication: new species in OBIGT, a FAQ vignette, a rewritten introduction, and more readable diagram labels.
◆ Where it's heading
2.0.0 was the structural break — Joules replacing calories as the default output of subcrt(), a required E_units column, a new model column, and the removal of a legacy scaling convention for heat-capacity coefficients. Everything since has built on that settled foundation rather than disturbing it. The direction of the last two releases is toward coverage of specific mineral systems, rare earths and uranyl among them, and toward making the package approachable, which suggests a maintainer courting new users rather than reworking the engine.
◆ Prediction
The next release most likely continues OBIGT curation for particular element systems plus vignette work; the highlights format gives no signal of engine-level changes pending.
surveycore
0.0INFRA · APIS
surveycore declared its API stable with every survey design type covered.
◆ Current state
surveycore is the estimation engine of a two-package survey stack, handling design objects and variance estimation while surveytidy supplies the dplyr verbs on top. The June release marks it 1.0.0 and states the API is complete and stable across Taylor series linearization, replicate weights, two-phase and non-probability designs, with means, totals, frequencies, quantiles, ratios, correlations, regression, t-tests, ANOVA and effective sample size all in place.
◆ Where it's heading
The last months before 1.0.0 were spent making the awkward designs behave like the ordinary ones. Non-probability designs gained jackknife replicate schemes and got their bootstrap repweights routed through the replicate-weight variance estimator in survey_glm(), matching every other estimation function. The survey_collection abstraction — several surveys treated as one pseudo-data-frame — was tightened rather than extended: divergent grouping across members now errors instead of stitching a patchwork with bind_rows(), and the missing-variable argument was renamed and given a stored default on the collection itself. A documentation audit before 1.0.0 turned up six dispatch and print bugs and corrections across forty-plus files, which is the kind of thing that surfaces when an API is being frozen rather than extended.
◆ Prediction
A declared-stable API means the next releases should be additive or corrective rather than breaking, and the pre-1.0.0 pattern of breaking renames should stop. The tight version pinning between the two packages means surveytidy releases will keep following surveycore's.
Alternatives to CHNOSZ and surveycore
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 CHNOSZ or surveycore.
NGINX
nginx returns to feature work with PROXY v2 upstream writes, and quietly adds JSON to core.
ESPHome
ESPHome closes the 2026.8 cycle, but the release body is a bare link to the real notes.
vcfR
A genomics workhorse whose visible release feed stops dead in mid-2020.
dialr
The R phone-number package stopped only parsing numbers and started asking them where they are.
ggVennDiagram
A Venn diagram package whose public release notes say almost nothing — including about its copyright cleanup.
See all CHNOSZ alternatives → · See all surveycore alternatives →
Recent activity from CHNOSZ and surveycore
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 2mo agosurveycoreFirst stable release: all four survey design types complete ⚡
- 3mo agosurveycoreget_effective_n() computes effective sample size
- 3mo agosurveycoreCollections error on divergent grouping; .on_missing renamed
- 4mo agosurveycoreCRAN patch removing surveytidy from the vignette
- 1y agoCHNOSZOBIGT gains rare earth and uranyl species; intro vignette rewritten
- 2y agoCHNOSZMosaic diagrams accept grouped basis species as variables
- 3y agoCHNOSZJoules become the default and the OBIGT schema is rebuilt ⚡
Frequently asked questions
What is the difference between CHNOSZ and surveycore?
They serve adjacent needs but don't currently overlap on shipped themes. CHNOSZ and surveycore 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 CHNOSZ better than surveycore?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. CHNOSZ and surveycore 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 CHNOSZ?
Top CHNOSZ alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "CHNOSZ alternatives" section above for the current picks, or visit /alternatives/chnosz for the full list with editorial commentary on each.
What are the best alternatives to surveycore?
Top surveycore alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "surveycore alternatives" section above for the current picks, or visit /alternatives/surveycore for the full list with editorial commentary on each.