Buildkite
Buildkite keeps converting hand-rolled agent workarounds into first-class CI primitives.
Comparison · Infra & APIs
stRoke vs tealeaves
A side-by-side editorial comparison of stRoke and tealeaves — release velocity, themes, recent moves, and the top alternatives to consider.
stRoke vs tealeaves: at a glance
What is stRoke?
Split itself in two, keeping the stroke-trial functions and exporting the rest
stRoke is now deliberately narrow: functions for handling clinical stroke trial data, mostly questionnaire scoring such as pase_calc() for PASE and mfi_calc() for MFI domain scores. It reached that state by subtraction — the 24.10.1 release moved eight general-purpose helpers out to a separate package, project.aid, and stated the change of focus in the notes. The most recent release, 25.9.1, is an eighty-character note about accommodating upcoming ggplot2 changes.
What is tealeaves?
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.
stRoke vs tealeaves: editorial side-by-side
stRoke
0.0INFRA · APIS
Split itself in two, keeping the stroke-trial functions and exporting the rest
◆ Current state
stRoke is now deliberately narrow: functions for handling clinical stroke trial data, mostly questionnaire scoring such as pase_calc() for PASE and mfi_calc() for MFI domain scores. It reached that state by subtraction — the 24.10.1 release moved eight general-purpose helpers out to a separate package, project.aid, and stated the change of focus in the notes. The most recent release, 25.9.1, is an eighty-character note about accommodating upcoming ggplot2 changes.
◆ Where it's heading
The package uses calendar versioning and its history is one of scope being repeatedly redrawn: ds2dd() went to REDCapCAST in 2023, then the general data and project management helpers went to project.aid in 2024. What remains is domain-specific and slow-moving, and the past eleven months produced a single compatibility release. The maintainer's visible effort has moved to the sibling packages.
◆ Prediction
Expect further questionnaire scoring functions if the maintainer's own trials need them and compatibility releases otherwise; on the pattern set in 24.10.1, more of the remaining general-purpose functions could still migrate to project.aid.
tealeaves
0.0INFRA · APIS
A leaf-temperature model that finished its job in 2020 and has stayed finished
◆ Current state
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.
◆ Where it's heading
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.
◆ Prediction
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.
Alternatives to stRoke and tealeaves
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 stRoke or tealeaves.
Cursor
Cursor's agents stop waiting to be asked - they subscribe, and they hold a goal until it's done.
incident.io
Nexus does the diagnosis; the agent is now reaching into the status page too.
Warp
Warp turned its quarter of software-factory essays into infrastructure you can buy.
Okta
Okta's developer blog is a Cross App Access campaign, now diluted by advocacy-team storytelling.
Infisical
A credential platform assembled two or three pull requests at a time, never a headline
See all stRoke alternatives → · See all tealeaves alternatives →
Recent activity from stRoke and tealeaves
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 10mo agostRokeCompatibility update for upcoming ggplot2 changes
- 1y agostRokeScope narrowed to stroke trials; eight helpers moved to project.aid ⚡
- 2y agostRokeChunking, string extraction and padding helpers added
- 3y agostRokeFix for ds2dd() after first practical use
- 3y agostRokePASE questionnaire scoring with data-quality checks
- 3y agostRokeFirst release: color_plot() built on contrast_text()
- 4y agotealeavesCitation file, vignette and README fixes
- 6y agotealeavesParameter-crossing bug fixed with tests; coverage added
- 6y agotealeavesFix for custom sky temperature function being overwritten
- 6y agotealeavesSky temperature as value or function; dplyr 1.0.0 compatibility
- 7y agotealeavesUnitless parameter values now accepted and assigned units
- 7y agotealeavesFirst release: leaf energy balance with per-surface conductances
Frequently asked questions
What is the difference between stRoke and tealeaves?
They serve adjacent needs but don't currently overlap on shipped themes. stRoke 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.
Is stRoke better than tealeaves?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. stRoke 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.
What are the best alternatives to stRoke?
Top stRoke alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "stRoke alternatives" section above for the current picks, or visit /alternatives/stroke for the full list with editorial commentary on each.
What are the best alternatives to tealeaves?
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.