Distributions.jl
Julia's distribution library keeps filing down the edges where sampling meets array types
A side-by-side editorial comparison of broom.helpers and OpenHouse — release velocity, themes, recent moves, and the top alternatives to consider.
After eleven quiet months, the tidier under gtsummary is back to absorbing model classes.
broom.helpers standardises the output of regression models so downstream packages can render them, and its release notes read as a running list of newly supported model classes. Version 1.23.0 ends an eleven-month silence — the longest gap in the visible history — with support for multi-state Cox models through an experimental tidy_coxphms(), plus a coefficient-type helper for brmsfit. The selector-removal arc that ran from 1.17.0 through 1.22.0 is finished, leaving the package narrowed to pure translation work.
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.
broom.helpers standardises the output of regression models so downstream packages can render them, and its release notes read as a running list of newly supported model classes. Version 1.23.0 ends an eleven-month silence — the longest gap in the visible history — with support for multi-state Cox models through an experimental tidy_coxphms(), plus a coefficient-type helper for brmsfit. The selector-removal arc that ran from 1.17.0 through 1.22.0 is finished, leaving the package narrowed to pure translation work.
The accretive arc is intact but slower than the release list alone suggests: five releases landed between January and September 2025, then nothing until this week. What resumed is the same pattern — one or two model classes per release, shipped as experimental tidiers first (coxphms here, svy_vglm in 1.21.0, vgam in 1.20.0) and hardened later. With the dot-prefixed selectors removed and the marginal-means tidiers deprecated, the package has stopped shedding scope and is back to only adding it. Whether cadence returns to 2025 levels or this is an isolated maintenance release is not readable from these entries.
The next release most likely promotes tidy_coxphms() out of experimental status or absorbs another survival-family or Bayesian model class, following the pattern of the last six. The entries give no signal on whether the eleven-month gap was a pause or a new baseline.
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 broom.helpers or OpenHouse.
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.
ggquiver is awake again, fixing arrow scaling that quietly misread irregular data.
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 broom.helpers 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 broom.helpers alternatives in Analytics are ranked by recent ship velocity. Browse the "broom.helpers alternatives" section above for the current picks, or visit /alternatives/broom-helpers 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.