Traefik
Traefik's 2.11 line spends August fixing the names it generates for Kubernetes resources.
A side-by-side editorial comparison of OpenRepGrid and surveycore — release velocity, themes, recent moves, and the top alternatives to consider.
Repertory grids learn which pole is the preferred one — a data-model change, not another plot option.
OpenRepGrid is the R toolkit for repertory grid analysis, the personal-construct-psychology technique of rating elements against bipolar constructs. Releases arrive every few months and the package passed JOSS review in late 2024. The current release, 0.1.18, is the largest in the window: a rebuilt import/export layer and the introduction of construct pole preference into the grid object itself.
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.
OpenRepGrid is the R toolkit for repertory grid analysis, the personal-construct-psychology technique of rating elements against bipolar constructs. Releases arrive every few months and the package passed JOSS review in late 2024. The current release, 0.1.18, is the largest in the window: a rebuilt import/export layer and the introduction of construct pole preference into the grid object itself.
The arc moves from presentation outward to the data model. 0.1.15 and 0.1.17 were about plots, colours, clustering options, and base-R ergonomics — subsetting by element name, cbind, names(). 0.1.18 changes what a grid can hold rather than how it is drawn, and threads that new attribute through import, construction, and analysis in one release. Getting data in and out is clearly the other priority: three dataframe layouts, long and wide Excel, multi-sheet import, workbook export.
With preferred poles now representable, the next likely step is analysis built on top of them — ideal-element distance and alignment measures — plus continued expansion of the import formats the package accepts.
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.
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.
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.
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 OpenRepGrid or surveycore.
Traefik's 2.11 line spends August fixing the names it generates for Kubernetes resources.
nginx returns to feature work with PROXY v2 upstream writes, and quietly adds JSON to core.
ESPHome closes the 2026.8 cycle, but the release body is a bare link to the real notes.
A genomics workhorse whose visible release feed stops dead in mid-2020.
The R phone-number package stopped only parsing numbers and started asking them where they are.
A Venn diagram package whose public release notes say almost nothing — including about its copyright cleanup.
See all OpenRepGrid alternatives → · See all surveycore alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. OpenRepGrid 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.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. OpenRepGrid 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.
Top OpenRepGrid alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "OpenRepGrid alternatives" section above for the current picks, or visit /alternatives/openrepgrid for the full list with editorial commentary on each.
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.