compositional.mle
An MLE package rebuilt around composable solvers, then renamed to match.
A side-by-side editorial comparison of kwb.geosalz and lazyeval — release velocity, themes, recent moves, and the top alternatives to consider.
A research-project workflow package where the interesting work is in the plumbing.
kwb.geosalz documents the data workflows for GeoSalz, a groundwater salinisation project run by Kompetenzzentrum Wasser Berlin, packaging retrieval, checking and plotting steps as reproducible R code. The current release replaces an SFTP dependency with curl and reports listing files on the SFTP server running 50 to 100 times faster. Earlier releases added data-availability workflows against Berlin's open water portal and functions for well-field abstraction figures.
A package retired in 2017 just got rewritten against R's public C API.
lazyeval was the tidyverse's pre-rlang non-standard evaluation layer, formally set aside in 2017 when tidy evaluation replaced it. After eight and a half years without a release, 0.2.3 arrives as a compliance rewrite: the implementation now uses R's public C API, and the release note states it may differ from the historical one in subtle ways. Nothing about the package's role has changed.
kwb.geosalz documents the data workflows for GeoSalz, a groundwater salinisation project run by Kompetenzzentrum Wasser Berlin, packaging retrieval, checking and plotting steps as reproducible R code. The current release replaces an SFTP dependency with curl and reports listing files on the SFTP server running 50 to 100 times faster. Earlier releases added data-availability workflows against Berlin's open water portal and functions for well-field abstraction figures.
Releases track the project's own data-collection reality rather than a software roadmap: new data source appears, a workflow is added; a transfer library becomes a liability, it is swapped out. The measurement-chain pipeline is the recurring subject, appearing in plotting fixes at 0.7.1 and the transport rewrite at 0.7.2. Cadence is roughly annual and the changelog is written for project members, which makes external readability secondary by design.
Expect the next release to follow the measurement-chain data as it accumulates, most likely more plotting or availability-checking work rather than new infrastructure.
lazyeval was the tidyverse's pre-rlang non-standard evaluation layer, formally set aside in 2017 when tidy evaluation replaced it. After eight and a half years without a release, 0.2.3 arrives as a compliance rewrite: the implementation now uses R's public C API, and the release note states it may differ from the historical one in subtle ways. Nothing about the package's role has changed.
This is a dormancy revival driven entirely from outside, R core tightening what counts as the public C API forces packages using older internals to be rewritten or be archived. lazyeval is still a dependency deep in older package trees, so keeping it installable matters more than developing it. The caveat about subtle behavioural differences is the notable part: a package nobody is developing has changed behaviour in ways its release note declines to enumerate.
Expect no further development, only additional compliance releases if R core tightens the C API again.
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 kwb.geosalz or lazyeval.
An MLE package rebuilt around composable solvers, then renamed to match.
nabla dropped its C++ engine to chase exact derivatives at any order.
Eight months from first release to keyring caching and workload identity.
A cyclomatic complexity checker that ships once every couple of years, and lands when it does.
Extreme value sampling in pure upkeep mode, mostly answering to Rcpp and CRAN.
patRoon 3.0.0 adds ion mobility, opening a dimension its workflows never had.
See all kwb.geosalz alternatives → · See all lazyeval alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. kwb.geosalz and lazyeval 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. kwb.geosalz and lazyeval 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 kwb.geosalz alternatives in Analytics are ranked by recent ship velocity. Browse the "kwb.geosalz alternatives" section above for the current picks, or visit /alternatives/kwb-geosalz for the full list with editorial commentary on each.
Top lazyeval alternatives in Analytics are ranked by recent ship velocity. Browse the "lazyeval alternatives" section above for the current picks, or visit /alternatives/lazyeval for the full list with editorial commentary on each.