r2dii.analysis
The climate-alignment maths behind PACTA, now stable and maintained rather than reshaped
A side-by-side editorial comparison of lazyeval and manymome — 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.
Steady quarterly releases behind a feed that shows almost none of what changed.
manymome computes indirect and moderated effects for path-analysis and SEM models using bootstrap and Monte Carlo intervals. The four most recent CRAN releases (0.3.2 through 0.3.6) publish as bare pointers to the package's own NEWS page, so the feed carries no changelog text for any of them. Where content is visible, at 0.3.1 and 0.2.9, the work is fitting-engine breadth and speed rather than new methodology.
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.
manymome computes indirect and moderated effects for path-analysis and SEM models using bootstrap and Monte Carlo intervals. The four most recent CRAN releases (0.3.2 through 0.3.6) publish as bare pointers to the package's own NEWS page, so the feed carries no changelog text for any of them. Where content is visible, at 0.3.1 and 0.2.9, the work is fitting-engine breadth and speed rather than new methodology.
The legible arc runs toward turning the q_* quick-mediation wrappers into a complete workflow: lavaan::sem fitting with full information maximum likelihood for missing data, a plot method, and user-specified mediation models, alongside repeated optimization of do_boot() and do_mc(). Cadence is roughly quarterly and has held for two years. What the last four versions actually contain cannot be read from this feed.
Expect continued quarterly CRAN releases extending the q_* family; beyond that the entries shown do not support a confident call on direction.
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 manymome.
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
A spin-out dictionary reader for MSF epidemiological data, finding its shape on CRAN
An MLE package rebuilt around composable solvers, then renamed to match.
nabla dropped its C++ engine to chase exact derivatives at any order.
See all lazyeval alternatives → · See all manymome alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. lazyeval and manymome 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 manymome 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 manymome alternatives in Analytics are ranked by recent ship velocity. Browse the "manymome alternatives" section above for the current picks, or visit /alternatives/manymome for the full list with editorial commentary on each.