mice
mice can finally predict, not just estimate, from multiply imputed data.
A side-by-side editorial comparison of ggfootball and incident.io — release velocity, themes, recent moves, and the top alternatives to consider.
A football-viz package just swapped scraping for an API and broke its own output to do it.
ggfootball is a small R package for plotting expected-goals and shot data, sourced from Understat. Four releases are visible. The 0.2.x line was argument tidying and dependency pruning; 0.3.0 replaced the data-acquisition layer wholesale, moving get_match_shots() from HTML parsing onto Understat's AJAX endpoints and changing the returned column names in the process.
Nexus does the diagnosis; the agent is now reaching into the status page too.
Investigations went generally available earlier this month, with Nexus posting a root-cause hypothesis and its evidence into the incident channel within minutes of declaration. The releases since have been the operational surround: a 24/7 schedule coverage policy that flags gaps before someone is missing from a rotation, more filtering in Insights, escalation reassignment, and now status page updates written by the agent alongside Pingdom uptime metrics and self-serve language settings.
ggfootball is a small R package for plotting expected-goals and shot data, sourced from Understat. Four releases are visible. The 0.2.x line was argument tidying and dependency pruning; 0.3.0 replaced the data-acquisition layer wholesale, moving get_match_shots() from HTML parsing onto Understat's AJAX endpoints and changing the returned column names in the process.
The direction is away from scraped HTML and toward a thinner, more defensible package: four dependencies dropped in 0.3.0 on top of qdapRegex in 0.2.1, input validation added, error messages rewritten. Both breaking changes so far were accepted rather than deferred, which reads as a maintainer treating pre-1.0 as the window to get the shape right. The package is willing to break callers for structural reasons, not cosmetic ones.
With the scraper rebuilt and the dependency surface trimmed, the next releases are likely to stabilise the new column names and extend the plotting side, which has seen nothing since 0.2.0. A 1.0 would be the signal that the data structure is now considered fixed.
Investigations went generally available earlier this month, with Nexus posting a root-cause hypothesis and its evidence into the incident channel within minutes of declaration. The releases since have been the operational surround: a 24/7 schedule coverage policy that flags gaps before someone is missing from a rotation, more filtering in Insights, escalation reassignment, and now status page updates written by the agent alongside Pingdom uptime metrics and self-serve language settings.
Two threads are converging. Nexus started inside the incident channel doing diagnosis, and it is now writing the customer-facing artifact as well — the status page is the first place its output leaves the responder's view and reaches the people affected. The rest is steady on-call plumbing: coverage policies, escalation routing, workflow secrets and signing. That split is consistent, with the agent taking judgment work and the platform hardening the mechanics around it.
Expect the agent to keep moving along the incident's outward path — customer comms, post-incident drafting — now that it writes to the status page, and expect more policy checks of the schedule-coverage kind that catch gaps before an incident finds them.
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 ggfootball or incident.io.
mice can finally predict, not just estimate, from multiply imputed data.
A market-microstructure toolkit that keeps adding estimators as the papers land.
A vowel-analysis package trimming dependencies after an email address got it archived.
The R half of the EMU speech database system, fixing what was quietly broken.
A Bayesian model-averaging package spending its 2.0 on memory, not methods.
tidyplots keeps rebuilding its own foundations rather than layering around them.
See all ggfootball alternatives → · See all incident.io alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. incident.io 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. incident.io 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 ggfootball alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "ggfootball alternatives" section above for the current picks, or visit /alternatives/ggfootball for the full list with editorial commentary on each.
Top incident.io alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "incident.io alternatives" section above for the current picks, or visit /alternatives/incident-io for the full list with editorial commentary on each.