Buildkite
Buildkite keeps converting hand-rolled agent workarounds into first-class CI primitives.
A side-by-side editorial comparison of ggh4x and tealeaves — release velocity, themes, recent moves, and the top alternatives to consider.
Handed its axis and legend guides to ggplot2 and legendry, and kept the facets
ggh4x is a set of ggplot2 extensions — nested and manual facets, per-facet scales, forced panel sizes, and statistics such as stat_difference() and stat_rle(). Its guide functions, once a substantial part of the package, are deprecated: 0.3.0 redirected users to ggplot2's own guide arguments and to the legendry package, and 0.3.1 made the deprecated functions return plain equivalents. What remains as this package's own territory is facetting and panel layout.
A leaf-temperature model that finished its job in 2020 and has stayed finished
tealeaves solves for leaf temperature from an energy balance, using explicit units to keep parameters consistent and modelling lower and upper leaf surfaces separately so sensible and latent heat loss are computed for each. The package reached its current form in 2020 across versions 1.0.2 to 1.0.5, which added direct or functional sky temperature, dplyr 1.0.0 compatibility, and fixes to a parameter-crossing bug that the new sky temperature function had introduced. The only release since, v1.0.6 in July 2022, corrects a name in the citation file, stops parallel evaluation in a vignette and fixes README links.
ggh4x is a set of ggplot2 extensions — nested and manual facets, per-facet scales, forced panel sizes, and statistics such as stat_difference() and stat_rle(). Its guide functions, once a substantial part of the package, are deprecated: 0.3.0 redirected users to ggplot2's own guide arguments and to the legendry package, and 0.3.1 made the deprecated functions return plain equivalents. What remains as this package's own territory is facetting and panel layout.
The handover was signalled well in advance. Version 0.2.5 set the guides' lifecycle to 'questioning' and said outright they might migrate to a new package once ggplot2 overhauled its guide system, and 0.3.0 executed that eighteen months later. Much of the rest of the changelog is anticipatory compatibility work for upcoming ggplot2 releases, the standing cost of being an extension package. Releases carry playful codenames that say nothing about their contents.
The deprecated guide functions are scheduled for removal in the next non-hotfix release, so expect that next; continued work should concentrate on facets and panel sizing, the areas neither ggplot2 nor legendry has absorbed.
tealeaves solves for leaf temperature from an energy balance, using explicit units to keep parameters consistent and modelling lower and upper leaf surfaces separately so sensible and latent heat loss are computed for each. The package reached its current form in 2020 across versions 1.0.2 to 1.0.5, which added direct or functional sky temperature, dplyr 1.0.0 compatibility, and fixes to a parameter-crossing bug that the new sky temperature function had introduced. The only release since, v1.0.6 in July 2022, corrects a name in the citation file, stops parallel evaluation in a vignette and fixes README links.
This is finished scientific software. The arc runs from a 1.0.0 that already described the full model, through a usability decision in 1.0.1 to accept unitless values and assign units rather than demand them, to a 2020 cluster of compatibility and correctness work around publication. Nothing since has touched the model, and the 2022 release is pure paperwork. Its most instructive entry remains 1.0.5, where a new feature silently produced incorrect parameter crossing and the fix arrived with tests to pin the behaviour.
Expect nothing unless a dependency or CRAN check forces a release; on this record any such release will be documentation and packaging rather than a change to the energy balance.
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 ggh4x or tealeaves.
Buildkite keeps converting hand-rolled agent workarounds into first-class CI primitives.
Cursor's agents stop waiting to be asked - they subscribe, and they hold a goal until it's done.
Nexus does the diagnosis; the agent is now reaching into the status page too.
Warp turned its quarter of software-factory essays into infrastructure you can buy.
Okta's developer blog is a Cross App Access campaign, now diluted by advocacy-team storytelling.
A credential platform assembled two or three pull requests at a time, never a headline
See all ggh4x alternatives → · See all tealeaves alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. ggh4x and tealeaves are shipping at a similar cadence (velocity 0.0 vs 0.0, both within Sparkpulse's "active" band). 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. ggh4x and tealeaves are shipping at a similar cadence (velocity 0.0 vs 0.0, both within Sparkpulse's "active" band). For your specific use case, the alternatives sections above list other Infra & APIs products to evaluate alongside.
Top ggh4x alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "ggh4x alternatives" section above for the current picks, or visit /alternatives/ggh4x for the full list with editorial commentary on each.
Top tealeaves alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "tealeaves alternatives" section above for the current picks, or visit /alternatives/tealeaves for the full list with editorial commentary on each.