broom.helpers
After eleven quiet months, the tidier under gtsummary is back to absorbing model classes.
A side-by-side editorial comparison of ggquiver and OpenHouse — release velocity, themes, recent moves, and the top alternatives to consider.
ggquiver is awake again, fixing arrow scaling that quietly misread irregular data.
A small ggplot2 extension for quiver and vector-field plots. The 0.3.x line in late 2021 made arrows behave outside plain Cartesian coordinates; after a four-year gap, 0.4.0 made them honour scale transformations and exposed grid::arrow() styling. 0.5.0 continues in correctness: automatic vecsize grid detection no longer rescales arrows wrongly on irregularly spaced data like GPS coordinates, an undetectable grid warns rather than errors, and legend keys now show an arrowhead.
OpenHouse starts adding per-column defaults while still closing silent-failure holes.
OpenHouse, LinkedIn's Iceberg control plane, is running two threads at once. A new [default values] work stream has begun landing - tables now apply server-supplied per-column defaults, with the read bridge updated to mark Iceberg bridge failures unrecoverable rather than letting them pass quietly. Alongside it, the safety work continues: orphan files now move to backup when a data manifest exists instead of being removed outright.
A small ggplot2 extension for quiver and vector-field plots. The 0.3.x line in late 2021 made arrows behave outside plain Cartesian coordinates; after a four-year gap, 0.4.0 made them honour scale transformations and exposed grid::arrow() styling. 0.5.0 continues in correctness: automatic vecsize grid detection no longer rescales arrows wrongly on irregularly spaced data like GPS coordinates, an undetectable grid warns rather than errors, and legend keys now show an arrowhead.
The consistent theme across both eras is deferring to ggplot2 rather than drawing on top of it — coordinate systems first, then scale transformations, then arrow styling handed to grid, and now the automatic sizing heuristic itself. The two 0.4.0/0.5.0 releases inside seven months suggest the four-year gap was dormancy rather than abandonment, and the work has shifted from integration gaps to the package's own inference: 0.5.0 is the first release to treat automatic grid detection as something that can be wrong rather than merely absent. The changelog remains entirely correctness and integration; there is still no sign of new plot types.
The entries support a narrow read: further releases will likely keep hardening vecsize inference and closing ggplot2 integration gaps as users report them. Two releases in seven months hint the cadence has resumed, but one gap of four years makes that weak evidence.
OpenHouse, LinkedIn's Iceberg control plane, is running two threads at once. A new [default values] work stream has begun landing - tables now apply server-supplied per-column defaults, with the read bridge updated to mark Iceberg bridge failures unrecoverable rather than letting them pass quietly. Alongside it, the safety work continues: orphan files now move to backup when a data manifest exists instead of being removed outright.
The month's pattern is unmistakable once the release titles are read together: CREATE OR REPLACE silently dropping table policies, RENAME COLUMN silently succeeding without renaming, RTAS not blocked on locked tables. This is a service systematically closing paths where a catalog operation reported success while losing metadata. The [default values] train is the first sustained additive capability in the window, and it is arriving as a sequence of narrow PRs rather than a single announced feature.
Expect further [default values] increments - write-path handling and validation are the obvious next pieces - before the capability is described as complete anywhere in the feed.
Other Analytics 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 ggquiver or OpenHouse.
After eleven quiet months, the tidier under gtsummary is back to absorbing model classes.
Julia's distribution library keeps filing down the edges where sampling meets array types
Power BI's monthly grind: authoring defaults, DAX documentation, and mobile finally catching up.
A lazy vector container keeps closing the gaps where it quietly materialised anyway.
Mesh interpolation drops its custom fork dependency and sheds weight.
A mesh renderer grows a scene graph and an exit route into glTF.
See all ggquiver alternatives → · See all OpenHouse alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. OpenHouse is currently shipping more aggressively (velocity 5.0 vs 2.5), 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. OpenHouse is currently shipping more aggressively (velocity 5.0 vs 2.5), with 0 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other Analytics products to evaluate alongside.
Top ggquiver alternatives in Analytics are ranked by recent ship velocity. Browse the "ggquiver alternatives" section above for the current picks, or visit /alternatives/ggquiver for the full list with editorial commentary on each.
Top OpenHouse alternatives in Analytics are ranked by recent ship velocity. Browse the "OpenHouse alternatives" section above for the current picks, or visit /alternatives/openhouse for the full list with editorial commentary on each.