enderecobr
Brazilian address standardisation moves its core to Rust, betting on throughput over pure R
A side-by-side editorial comparison of lazyeval and TrialEmulation — 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.
Target trial emulation held steady by dependency maintenance, not new methods.
TrialEmulation implements target trial emulation from observational data, using duckdb to handle the expanded per-period datasets that approach generates. Every release in the visible window is upkeep: two consecutive releases removing the archived parglm dependency, two fixing tests against testthat updates, and two tracking duckdb sampling changes. No methodological work appears in the feed since before February 2025.
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.
TrialEmulation implements target trial emulation from observational data, using duckdb to handle the expanded per-period datasets that approach generates. Every release in the visible window is upkeep: two consecutive releases removing the archived parglm dependency, two fixing tests against testthat updates, and two tracking duckdb sampling changes. No methodological work appears in the feed since before February 2025.
The package is being kept installable rather than extended. Its dependency surface, duckdb for storage, parglm for fitting, testthat for checks, generates most of the release traffic, and CRAN archiving parglm forced two separate releases three months apart to fully excise it. The version numbering, still in the 0.0.4.x range after years, suggests the maintainers do not consider the API settled enough to promote.
Further releases will most likely be triggered by upstream dependency changes; the entries give no signal on when methodological work resumes.
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 TrialEmulation.
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
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.
See all lazyeval alternatives → · See all TrialEmulation alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — maintenance — within Analytics. lazyeval and TrialEmulation 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 TrialEmulation 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 TrialEmulation alternatives in Analytics are ranked by recent ship velocity. Browse the "TrialEmulation alternatives" section above for the current picks, or visit /alternatives/trialemulation for the full list with editorial commentary on each.