RSelenium
RSelenium's only release in eight years touched documentation and CI, nothing else.
A side-by-side editorial comparison of Resend and waldo — release velocity, themes, recent moves, and the top alternatives to consider.
Resend is wiring itself into every agent runtime it can reach, one standard at a time
Almost every recent entry is about who or what can call Resend rather than about email delivery itself: OAuth 2.1 with PKCE, a remote MCP server tracking the current spec, a Codex plugin, a one-click Claude connector, and now support for the Agent Plugins Standard. The email product still gets attention — suppressions, template folders, a compatibility checker in the code editor — but it is the smaller half of the feed. Entries are terse one-liners, so the shipping cadence reads faster than the surface area actually changing.
waldo keeps shedding dependencies while teaching its diff engine new object systems
waldo produces the object comparisons that testthat failure messages are built from. The recent releases do two things: drop dependencies - tibble, rematch2 and fansi have all gone - and extend comparison to object systems that did not exist when it was written, notably S7. Correctness of missing-value and tolerance semantics accounts for most of the rest.
Almost every recent entry is about who or what can call Resend rather than about email delivery itself: OAuth 2.1 with PKCE, a remote MCP server tracking the current spec, a Codex plugin, a one-click Claude connector, and now support for the Agent Plugins Standard. The email product still gets attention — suppressions, template folders, a compatibility checker in the code editor — but it is the smaller half of the feed. Entries are terse one-liners, so the shipping cadence reads faster than the surface area actually changing.
Resend is treating agents as the next class of sending client and building the authorization and discovery plumbing they need before that traffic arrives. The progression is legible: first authenticate third parties (OAuth), then be callable (MCP), then be installable per vendor (Codex, Claude), and now be installable by standard. The developer-experience work — secret scanning, email-client compatibility warnings, Message-ID threading — keeps the human-facing product credible while that shift happens.
Having covered authorization and discovery, the gap left is what an agent is permitted to send once connected; scoped, per-agent sending limits or approval controls are the natural next piece.
waldo produces the object comparisons that testthat failure messages are built from. The recent releases do two things: drop dependencies - tibble, rematch2 and fansi have all gone - and extend comparison to object systems that did not exist when it was written, notably S7. Correctness of missing-value and tolerance semantics accounts for most of the rest.
This is a package deliberately shrinking its footprint while widening what it understands. Since it is imported by testthat, every dependency it drops is one fewer package in the check environment of most of CRAN, which is clearly the motivation. The comparison logic itself changes only when R gains a new way to represent objects.
Expect S7 support to deepen from basic to complete as S7 adoption grows, and further dependency removals; the diff algorithm itself looks settled.
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 Resend or waldo.
RSelenium's only release in eight years touched documentation and CI, nothing else.
servr keeps growing from a static file server into a general-purpose R web server.
Rhino's release line runs on release candidates, and 1.12 makes room for coding agents.
Windmill is dismantling the paywall between itself and the data stack
vdiffr finished its job in 2021 and has been tracking compilers ever since.
The deployment client is being rebuilt around credentials it never has to store.
See all Resend alternatives → · See all waldo alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Resend is currently shipping more aggressively (velocity 6.3 vs 0.0), with 1 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. Resend is currently shipping more aggressively (velocity 6.3 vs 0.0), with 1 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 Resend alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Resend alternatives" section above for the current picks, or visit /alternatives/resend for the full list with editorial commentary on each.
Top waldo alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "waldo alternatives" section above for the current picks, or visit /alternatives/waldo for the full list with editorial commentary on each.