paleobuddy
paleobuddy can now simulate trait-dependent diversification, not just birth-death.
A side-by-side editorial comparison of broman and Dagster — release velocity, themes, recent moves, and the top alternatives to consider.
A statistician's personal toolbox, growing one plotting utility at a time
broman is Karl Broman's collection of personal R utilities — base-graphics plotting helpers such as grayplot, dotplot and timeplot, running-window summaries, and assorted conveniences. Recent releases alternate between small additions, like runningratio2() with an adaptive window sized to hit a target denominator, and narrow bug fixes in crayons() and jiggle(). Version 0.92 removes an include that had begun warning on CRAN.
Dagster is turning declarative automation from an asset feature into the way the whole platform schedules work.
Dagster ships a core/libraries pair on a near-weekly cadence, and the release notes read like an engineering log: a few genuinely new capabilities per version, a long bugfix tail, and steady community contributions. The current cycle is concentrated in three places — Declarative Automation, the dbt-on-Snowflake integration, and asset health reporting. Serverless and Kubernetes deployment paths get frequent hardening.
broman is Karl Broman's collection of personal R utilities — base-graphics plotting helpers such as grayplot, dotplot and timeplot, running-window summaries, and assorted conveniences. Recent releases alternate between small additions, like runningratio2() with an adaptive window sized to hit a target denominator, and narrow bug fixes in crayons() and jiggle(). Version 0.92 removes an include that had begun warning on CRAN.
The additions cluster around two themes: time-axis plotting and running-window summaries, both of which have been extended across several releases. Nothing here is planned in the usual sense — functions appear when the author needs them and bugs are fixed when they surface downstream, as jiggle() did through dotplot(). The C-level cleanup in 0.92 matches the same change made to R/qtl the same week, which is what maintaining a set of packages under one author looks like.
Both recent function additions extend existing families rather than starting new ones, so the next release is most likely another variant in the running-window or time-plotting group, or a fix surfaced by one of the author's other packages.
Dagster ships a core/libraries pair on a near-weekly cadence, and the release notes read like an engineering log: a few genuinely new capabilities per version, a long bugfix tail, and steady community contributions. The current cycle is concentrated in three places — Declarative Automation, the dbt-on-Snowflake integration, and asset health reporting. Serverless and Kubernetes deployment paths get frequent hardening.
Declarative Automation is expanding past its original asset scope: it can now launch entire jobs from a condition, with its own evaluation history tab. In parallel, the component model is becoming the packaging unit for integrations, with SnowflakeDbtProjectComponent moving from preview toward parity with DbtCloudComponent via versioned state storage. Asset health is being made more honest — failures pending an automatic retry now warn rather than report degraded, so alerts stop crying wolf.
Declarative Automation for jobs is the clearest candidate to graduate from preview, and SnowflakeDbtProjectComponent is following the same preview-to-parity path. Expect the component surface to keep absorbing integrations that were previously bespoke code.
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 broman or Dagster.
paleobuddy can now simulate trait-dependent diversification, not just birth-death.
geodist stays dependency-free and fast, and warns you when 'cheap' distances stop being honest.
errors keeps making uncertainty print the way each scientific field expects.
CMAQ went global in v5.5, and has been patching that surface ever since.
enpls has not changed its statistics since 2016 — only its website, twice.
grex is a lookup table with a version number — it ships when the annotation moves.
See all broman alternatives → · See all Dagster alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Dagster 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. Dagster 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 Analytics products to evaluate alongside.
Top broman alternatives in Analytics are ranked by recent ship velocity. Browse the "broman alternatives" section above for the current picks, or visit /alternatives/broman-r for the full list with editorial commentary on each.
Top Dagster alternatives in Analytics are ranked by recent ship velocity. Browse the "Dagster alternatives" section above for the current picks, or visit /alternatives/dagster for the full list with editorial commentary on each.