Cronicle
The job scheduler's release stream is now almost entirely vulnerability patching and authorization hardening.
Comparison · Infra & APIs
evaluate vs packrat
A side-by-side editorial comparison of evaluate and packrat — release velocity, themes, recent moves, and the top alternatives to consider.
Shared themes:reproducibilityr-package
evaluate vs packrat: at a glance
What is evaluate?
The engine under every knitted R document reached 1.0 by making evaluation behave like the console.
evaluate captures the output, plots, messages and conditions produced by running R code, and it is the layer knitr and R Markdown sit on. The 1.0.0 release changed core semantics — multi-expression input now stops at the first error — and gave results a real class. Since then, releases have been graphics-focused: ragg-based capture when available, grid plot fixes, and a patch for ggplot2 4.0.0.
What is packrat?
R's old dependency manager now runs on a vendored copy of its own successor.
packrat was R's project dependency manager before renv replaced it, and its recent releases describe a package in careful retirement. It vendors renv internally and uses it for dependency detection and authenticated downloads, so several release notes amount to updating that bundled copy. The remaining work is repository plumbing: recognising Bioconductor packages that now carry a Repository field, handling CRAN-like, Nexus and older Artifactory archive layouts, and renaming downloads from r-universe that do not follow the expected filename pattern.
evaluate vs packrat: editorial side-by-side
evaluate
0.0INFRA · APIS
The engine under every knitted R document reached 1.0 by making evaluation behave like the console.
◆ Current state
evaluate captures the output, plots, messages and conditions produced by running R code, and it is the layer knitr and R Markdown sit on. The 1.0.0 release changed core semantics — multi-expression input now stops at the first error — and gave results a real class. Since then, releases have been graphics-focused: ragg-based capture when available, grid plot fixes, and a patch for ggplot2 4.0.0.
◆ Where it's heading
The package is being tightened rather than expanded. 1.0.0 removed complexity it could not justify, deprecated include_timing, dropped a function testing for an object it never created, and aligned error behaviour with the console; 1.0.4 then moved plot capture toward a faster, more capable device. The recurring theme is reliability of output capture across environments, which is exactly what a document-rendering substrate needs and what local_reproducible_output() exists to enforce.
◆ Prediction
Expect continued fast-follow patches keyed to graphics-stack releases — ggplot2 and ragg in particular — rather than new API surface.
packrat
0.0INFRA · APIS
R's old dependency manager now runs on a vendored copy of its own successor.
◆ Current state
packrat was R's project dependency manager before renv replaced it, and its recent releases describe a package in careful retirement. It vendors renv internally and uses it for dependency detection and authenticated downloads, so several release notes amount to updating that bundled copy. The remaining work is repository plumbing: recognising Bioconductor packages that now carry a Repository field, handling CRAN-like, Nexus and older Artifactory archive layouts, and renaming downloads from r-universe that do not follow the expected filename pattern.
◆ Where it's heading
Development here is about keeping existing projects restorable rather than making packrat a better choice for new ones. Nearly every entry is a fix for an environment that changed underneath it — a repository layout, a service's authentication scheme, a distribution's URL format. The vendoring of renv is the clearest statement of direction: the successor's logic is doing the work, wrapped in the old interface.
◆ Prediction
Expect further releases only when package repositories change shape or the vendored renv needs refreshing, at roughly the two-year cadence the recent history shows. Nothing suggests new capability, and the practical migration path remains renv itself.
Alternatives to evaluate and packrat
Other Infra & APIs 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 evaluate or packrat.
Helm
Helm runs two release trains in lockstep while v3 walks toward end-of-life.
goodpractice
The R package-quality checker returns from CRAN limbo with checks you can select by category.
quarto
Quarto's editor extension is quietly becoming Positron-first while keeping VS Code parity.
q2
Ten releases in six days, methodically porting Quarto's surface into a Rust binary.
pkgcache
The metadata cache under pak now speaks to authenticated and corporate repositories.
See all evaluate alternatives → · See all packrat alternatives →
Recent activity from evaluate and packrat
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 11mo agoevaluatePatch for ggplot2 4.0.0 support
- 1y agoevaluatePlot capture moves to ragg when available
- 1y agopackratHandles Bioconductor detection and varied repository layouts
- 1y agoevaluateFix for rlang::abort() inside evaluate()
- 1y agoevaluate1.0 stops at the first error and gives results a class ⚡
- 2y agoevaluateSource handler gains access to the parsed call
- 3y agopackratRestores packages installed from repository subdirectories
- 3y agopackratPrivate repository restores; git credentials masked from installs
- 4y agopackratGitLab private repos authenticate via GITLAB_PAT
- 4y agopackratBundles renv for dependency detection; adds authenticated downloads
- 4y agopackratBreaking: cache directory now includes an R version suffix
Frequently asked questions
What is the difference between evaluate and packrat?
Both compete on the same themes — reproducibility, r-package — within Infra & APIs. evaluate and packrat 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.
Is evaluate better than packrat?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. evaluate and packrat 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 Infra & APIs products to evaluate alongside.
What are the best alternatives to evaluate?
Top evaluate alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "evaluate alternatives" section above for the current picks, or visit /alternatives/evaluate for the full list with editorial commentary on each.
What are the best alternatives to packrat?
Top packrat alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "packrat alternatives" section above for the current picks, or visit /alternatives/packrat for the full list with editorial commentary on each.