EvoPhylo
EvoPhylo added BEAST2 alongside MrBayes, then went quiet for two years.
A side-by-side editorial comparison of geos and redist — release velocity, themes, recent moves, and the top alternatives to consider.
The thin GEOS binding for R adds terra interop after three years of compiler triage
geos is a low-overhead R binding to the GEOS geometry engine, exposing predicates, overlays and spatial indexes with minimal copying. Version 0.2.5 accepts terra SpatVector objects directly, alongside fixes for zero-length memcpy and plotting of invalid geometries. The releases between 0.2.0 and 0.2.5 contain almost no feature work — they are responses to compiler warnings, sanitiser findings and CRAN check failures.
redist keeps rewriting the sampler underneath a district-drawing API it has held stable since 4.0.
redist simulates redistricting plans via sequential Monte Carlo, merge-split MCMC and short-burst optimization, and it is the analysis tool behind a good deal of published districting work. The user-facing shape was set by 4.0.1's constraint interface and the split of metrics into the redistmetrics package; since then the changes are in the algorithms. The most consequential recent one replaces the SMC label-counting adjustment with a backward kernel that removes approximation error outright.
geos is a low-overhead R binding to the GEOS geometry engine, exposing predicates, overlays and spatial indexes with minimal copying. Version 0.2.5 accepts terra SpatVector objects directly, alongside fixes for zero-length memcpy and plotting of invalid geometries. The releases between 0.2.0 and 0.2.5 contain almost no feature work — they are responses to compiler warnings, sanitiser findings and CRAN check failures.
Feature development stopped after 0.2.0 and the package has since been kept alive against a moving toolchain: strict-prototypes warnings, a clang sanitiser error, format string checks, an M1 test failure. The 0.2.5 terra support breaks that pattern and came from an outside contributor, which suggests the package's direction is now set by what neighbouring spatial packages need from it rather than by GEOS feature coverage.
GEOS has released new capabilities since the 3.11 features wired up in 0.2.0, and none have been exposed since; whether the next release closes that gap or continues as interop-and-maintenance is the open question the history does not yet answer.
redist simulates redistricting plans via sequential Monte Carlo, merge-split MCMC and short-burst optimization, and it is the analysis tool behind a good deal of published districting work. The user-facing shape was set by 4.0.1's constraint interface and the split of metrics into the redistmetrics package; since then the changes are in the algorithms. The most consequential recent one replaces the SMC label-counting adjustment with a backward kernel that removes approximation error outright.
The direction is toward exactness and throughput at once — the new kernel is described as both eliminating approximation error and costing far less computation, and successive releases keep adding parallelism, most recently to the flip algorithm. Feature growth has moved into the optimization side, where short-burst gained multiple independent scorers and a Pareto frontier. The release notes are not a reliable ledger: 4.3.1 ships the identical text as 4.3.0.
Expect the remaining single-threaded algorithms to gain the chains-style parallelism that flip just received, following the pattern SMC established several releases ago.
Other Analytics 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 geos or redist.
EvoPhylo added BEAST2 alongside MrBayes, then went quiet for two years.
treespace ships once every year or two, and only when CRAN or a user forces it.
Rpath 1.1.0 learns to read Ecopath's own files, easing migration off the desktop tool.
TAF keeps turning ICES stock assessments into reproducible, dependency-pinned projects.
parallelDist is in pure preservation mode — one build fix every few years.
Cairo finally catches R's graphics engine, all the way to GE API 16.
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. geos and redist 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. geos and redist 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 Analytics products to evaluate alongside.
Top geos alternatives in Analytics are ranked by recent ship velocity. Browse the "geos alternatives" section above for the current picks, or visit /alternatives/geos-r for the full list with editorial commentary on each.
Top redist alternatives in Analytics are ranked by recent ship velocity. Browse the "redist alternatives" section above for the current picks, or visit /alternatives/redist-r for the full list with editorial commentary on each.