httpuv
httpuv ships almost nothing, which is what you want from the web server under Shiny
A side-by-side editorial comparison of distributed and htmltools — release velocity, themes, recent moves, and the top alternatives to consider.
Dask's scheduler spent the year deleting deprecated API, not adding surface.
distributed is cutting frequent tags with little in them. The substantive release in the window is 2026.6.0, which removed deprecations across the scheduler, worker, nanny, CLI, security and deploy modules in roughly twenty separate cleanups and moved CI to pixi. 2026.7.0 follows with a breaking scatter change and a scheduler_info() default change; the two most recent tags are a backport and an empty release with no changes at all.
htmltools spends three releases walking back its own fill-layout opinions
htmltools generates the HTML that Shiny, bslib and R Markdown emit. Recent releases are dominated by one project - the fill and fillable layout system that powers bslib cards - being tuned release after release, surrounded by fixes for whatever testthat or R-devel changed underneath.
distributed is cutting frequent tags with little in them. The substantive release in the window is 2026.6.0, which removed deprecations across the scheduler, worker, nanny, CLI, security and deploy modules in roughly twenty separate cleanups and moved CI to pixi. 2026.7.0 follows with a breaking scatter change and a scheduler_info() default change; the two most recent tags are a backport and an empty release with no changes at all.
The direction is consolidation. A single maintainer is systematically retiring API that had been deprecated for years, tightening type annotations and chasing flaky tests, while the feature surface stays flat. Python 3.14 support and a PyArrow floor in 2026.1.2 fit the same pattern of keeping the runtime current rather than extending it.
With the deprecation sweep largely done and pixi now driving CI, the next releases most likely continue as small breaking cleanups on top of a stable feature set rather than introducing new scheduler capability.
htmltools generates the HTML that Shiny, bslib and R Markdown emit. Recent releases are dominated by one project - the fill and fillable layout system that powers bslib cards - being tuned release after release, surrounded by fixes for whatever testthat or R-devel changed underneath.
The fill work is converging rather than expanding: 0.5.6 stopped forcing overflow on fillable containers, 0.5.7 stopped forcing full width on fill items, and 0.5.8 lowered the CSS's precedence by moving it into a named cascade layer. Each step removes an opinion that broke someone's layout. The two most recent releases add nothing at all beyond test compatibility.
With the fill CSS now scoped to its own cascade layer, expect fewer layout corrections and a continued pattern of small releases driven by testthat and R-devel rather than new API.
Other DevOps 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 distributed or htmltools.
httpuv ships almost nothing, which is what you want from the web server under Shiny
promises drops R6 for plain environments and wires async work into OpenTelemetry
withr rebuilt defer() on base R's own on.exit(), and got much faster for it
xml2 relicensed to MIT, then moved its hot accessors from S3 into C
httr's last releases are housekeeping - the package now points users at httr2
magrittr rewrote its pipe in C, then base R shipped one and the releases stopped
See all distributed alternatives → · See all htmltools alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — maintenance — within DevOps. distributed is currently shipping more aggressively (velocity 5.0 vs 0.0), 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. distributed is currently shipping more aggressively (velocity 5.0 vs 0.0), with 0 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other DevOps products to evaluate alongside.
Top distributed alternatives in DevOps are ranked by recent ship velocity. Browse the "distributed alternatives" section above for the current picks, or visit /alternatives/dask-distributed for the full list with editorial commentary on each.
Top htmltools alternatives in DevOps are ranked by recent ship velocity. Browse the "htmltools alternatives" section above for the current picks, or visit /alternatives/htmltools for the full list with editorial commentary on each.