Resend
Resend is wiring itself into every agent runtime it can reach, and now adding the controls to stop a send.
A side-by-side editorial comparison of bolasso and DNSControl — release velocity, themes, recent moves, and the top alternatives to consider.
Bootstrap lasso got a fast mode, a second selection rule, and multinomial support
bolasso implements the bootstrapped lasso, refitting a regularized regression across bootstrap replicates and selecting variables by how consistently they survive. The 0.3.0 release reshaped it: a fast argument computes one cross-validated lambda on the full dataset instead of cross-validating inside every replicate, and selected_variables() gained a choice between the variable inclusion probability rule and a quantile rule based on bootstrap confidence intervals. Since then 0.4.0 exposed the bootstrap indices through bootstrap_samples(), and 0.5.0 extended the whole surface to multinomial responses, returning one list element per outcome level.
DNSControl v5 is feature-frozen with a ship date, and rc9 is pure provider cleanup
DNSControl has locked v5.0.0 to bugfixes only with a stated ship date of 25 August 2026. rc9 carries no new capability: punycode decoding before IDNA validation in ALIDNS, a SVCB fix in POWERDNS, NAPTR and trailing-dot fixes in DYNU, a dnssort edge case, and internal refactors replacing pkg/diff and standardising on models.Records. The release notes read as a call for provider testing more than an announcement.
bolasso implements the bootstrapped lasso, refitting a regularized regression across bootstrap replicates and selecting variables by how consistently they survive. The 0.3.0 release reshaped it: a fast argument computes one cross-validated lambda on the full dataset instead of cross-validating inside every replicate, and selected_variables() gained a choice between the variable inclusion probability rule and a quantile rule based on bootstrap confidence intervals. Since then 0.4.0 exposed the bootstrap indices through bootstrap_samples(), and 0.5.0 extended the whole surface to multinomial responses, returning one list element per outcome level.
The package spent 2022 dormant after its initial releases and has been actively developed since late 2024, moving from a single algorithm toward a workbench. The additions cluster around inspection rather than estimation: tidy() for bootstrap-level coefficients, plot_selection_thresholds() for selection stability across thresholds, plot_selected_variables() for the surviving covariates, and now the extracted bootstrap indices. Documented gaps remain, with mgaussian unsupported and multinomial prediction limited to class output.
The two stated limitations in 0.5.0 - no mgaussian family and class-only multinomial prediction - are the most likely next targets, since the maintainer flagged both as possible later additions.
DNSControl has locked v5.0.0 to bugfixes only with a stated ship date of 25 August 2026. rc9 carries no new capability: punycode decoding before IDNA validation in ALIDNS, a SVCB fix in POWERDNS, NAPTR and trailing-dot fixes in DYNU, a dnssort edge case, and internal refactors replacing pkg/diff and standardising on models.Records. The release notes read as a call for provider testing more than an announcement.
The v5 arc has run its course in public: rc1 laid out the dnsv2.RDATA refactor, rc3 finished converting every provider to it, rc4 completed the move to the Codeberg-hosted miekg/dns, and rc8 declared feature completeness. What is left is per-provider correctness on record types that only a handful of users exercise, which is why the maintainer is publishing a list of which providers most need testing rather than shipping.
Expect one or two more release candidates of provider fixes before the 25 August date, with the risk concentrated in providers nobody volunteers to test - the notes already flag PACKETFRAME as unmaintained and EXOSCALE as not supporting PTR.
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 bolasso or DNSControl.
Resend is wiring itself into every agent runtime it can reach, and now adding the controls to stop a send.
Casdoor is spending its release cadence moving auth checks from the client to the server
ESPHome ships on a calendar, and the August beta train is now five builds deep
Strimzi's 1.2.0 candidate closes with a logging fix and nothing else
Prowler's assistant decides what to do with findings; the patches keep the scanner honest
NetBox adds a cooling data model — the first new infrastructure domain since power
See all bolasso alternatives → · See all DNSControl alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. DNSControl is currently shipping more aggressively (velocity 5.0 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. DNSControl is currently shipping more aggressively (velocity 5.0 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 bolasso alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "bolasso alternatives" section above for the current picks, or visit /alternatives/bolasso for the full list with editorial commentary on each.
Top DNSControl alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "DNSControl alternatives" section above for the current picks, or visit /alternatives/dnscontrol for the full list with editorial commentary on each.