cIRT
A choice-based IRT model published once in 2019 and kept compiling ever since
A side-by-side editorial comparison of itp and lazyeval — release velocity, themes, recent moves, and the top alternatives to consider.
A single-algorithm root-finder that finished its job in 2022 and has been idling since
itp implements one thing: the Interpolate, Truncate, Project root-finding algorithm of Oliveira and Takahashi, which narrows a bracketing interval each iteration and keeps bisection's worst-case guarantee while converging faster on well-behaved functions. The package reached its intended shape within about six weeks of first release, gaining a C++ entry point and the ability to take C++ function pointers. Everything after mid-2022 is compiler and CRAN upkeep.
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.
itp implements one thing: the Interpolate, Truncate, Project root-finding algorithm of Oliveira and Takahashi, which narrows a bracketing interval each iteration and keeps bisection's worst-case guarantee while converging faster on well-behaved functions. The package reached its intended shape within about six weeks of first release, gaining a C++ entry point and the ability to take C++ function pointers. Everything after mid-2022 is compiler and CRAN upkeep.
The arc is short and complete. Three releases in June and July 2022 took the package from an R implementation to one that can run the whole algorithm in C++ and accept user-supplied C++ functions via Rcpp's external pointer framework. Since then the only releases have been reactions to Rcpp changes that would otherwise trip CRAN checks — 2023 and 2026, both traceable to specific upstream Rcpp issues.
There is no visible development agenda here; the entries suggest the package surfaces only when Rcpp or CRAN check policy forces a patch.
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 itp or lazyeval.
A choice-based IRT model published once in 2019 and kept compiling ever since
The R engine behind MetaboAnalyst closes the gap from raw spectra to biological interpretation
Rebuilding SAS's formatting layer in R, one format specification at a time
Standardised coefficients for models where standardising everything is wrong — but the feed only links out
Stream-network spatial models learning to run on data that no longer fits in memory
Bioconductor's installer, frozen at 1.30.x and tuned almost entirely through environment variables
See all itp 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. itp 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. itp 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 itp alternatives in Analytics are ranked by recent ship velocity. Browse the "itp alternatives" section above for the current picks, or visit /alternatives/itp 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.