q2
Ten releases in six days, methodically porting Quarto's surface into a Rust binary.
A side-by-side editorial comparison of evaluate and gh — release velocity, themes, recent moves, and the top alternatives to consider.
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.
gh spent its last two releases making failures and interruptions recoverable.
The GitHub API client rebuilt on httr2 in 1.4.0, then took a security-driven breaking change in 1.5.0: response headers are no longer stored in returned objects, because they can carry sensitive information. The 1.6.0 release made interrupted pagination recoverable and downgraded personal access token format validation from an error to a warning.
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.
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.
Expect continued fast-follow patches keyed to graphics-stack releases — ggplot2 and ragg in particular — rather than new API surface.
The GitHub API client rebuilt on httr2 in 1.4.0, then took a security-driven breaking change in 1.5.0: response headers are no longer stored in returned objects, because they can carry sensitive information. The 1.6.0 release made interrupted pagination recoverable and downgraded personal access token format validation from an error to a warning.
The direction is tolerance for partial and unusual outcomes rather than new endpoint coverage. Interrupting a paginated call now raises a classed condition carrying the records already fetched; a 304 Not Modified returns an empty response with headers intact instead of erroring; an unrecognised token format warns and proceeds. A fake_github_app() built on webfakes ships for testing, and is offered to other package authors.
Token format handling is now configurable rather than fixed, so the next likely work is following GitHub's credential formats as they change, not expanding the client surface.
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 gh.
Ten releases in six days, methodically porting Quarto's surface into a Rust binary.
The metadata cache under pak now speaks to authenticated and corporate repositories.
R's old dependency manager now runs on a vendored copy of its own successor.
A fake web server for tests that keeps closing the gap with the real thing.
Hit 1.0, relicensed to MIT, and has shipped almost nothing but dbplyr compatibility since.
carrier's 0.3.0 quietly rewrites how crated functions see each other — and breaks code that relied on the old rules.
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. gh is currently shipping more aggressively (velocity 2.5 vs 0.0), with 0 editorial sparks in the last 30 days against 0. 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. gh is currently shipping more aggressively (velocity 2.5 vs 0.0), with 0 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other Infra & APIs products to evaluate alongside.
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.
Top gh alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "gh alternatives" section above for the current picks, or visit /alternatives/gh for the full list with editorial commentary on each.