BORG
A cross-validation guard that refuses to run random CV on dependent data unless you insist
A side-by-side editorial comparison of lazyeval and popbayes — release velocity, themes, recent moves, and the top alternatives to consider.
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.
A wildlife population-trend package in low-maintenance mode.
popbayes fits Bayesian trends to animal population count series that mix ground counts, aerial counts and expert estimates. The visible history is short and slow: three releases across four years, with the most recent, 1.3, swapping usethis for cli in error messages and tidying the website. The substantive work in the window is 1.1, which reorganised how format_data() handles a dataset.
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.
popbayes fits Bayesian trends to animal population count series that mix ground counts, aerial counts and expert estimates. The visible history is short and slow: three releases across four years, with the most recent, 1.3, swapping usethis for cli in error messages and tidying the website. The substantive work in the window is 1.1, which reorganised how format_data() handles a dataset.
Development has settled into maintenance carried largely by outside contributors, with the current release consisting of a dependency swap and message fixes from two different contributors. The one release with real design work, 1.1, moved format_data() from operating on a whole dataset to operating per count series, letting different series of the same species carry different conversion assumptions. Nothing since has changed the modelling surface.
The entries do not support a confident prediction beyond further contributor-driven maintenance; there is no visible signal of new modelling work.
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 lazyeval or popbayes.
A cross-validation guard that refuses to run random CV on dependent data unless you insist
A single-algorithm root-finder that finished its job in 2022 and has been idling since
Brazilian address standardisation moves its core to Rust, betting on throughput over pure R
The climate-alignment maths behind PACTA, now stable and maintained rather than reshaped
A decade-old droplet PCR analysis package woken up for one compatibility release
A Bayesian ratio-modelling package that threw out its Stan dependency and wrote its own sampler
See all lazyeval alternatives → · See all popbayes alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — maintenance — within Analytics. lazyeval and popbayes 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. lazyeval and popbayes 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 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.
Top popbayes alternatives in Analytics are ranked by recent ship velocity. Browse the "popbayes alternatives" section above for the current picks, or visit /alternatives/popbayes for the full list with editorial commentary on each.