stringr
stringr keeps trading convenient guesses for predictable errors.
A side-by-side editorial comparison of plumber and uproot5 — release velocity, themes, recent moves, and the top alternatives to consider.
R's API framework grew its serializer catalogue, then went quiet on features.
plumber is at 1.3.3, and the last three releases are small: a Swagger redirect fix for hosted environments, a test-robustness change, and Arrow IPC Streams serializers. The feature weight sits further back — 1.3.0 added excel serializers and parsers, ragg and svglite graphics devices, port validation against IANA ranges, and stopped writing parsed bodies to disk.
Uproot quietly made RNTuple the default write format — filed under 'chore'.
Uproot ships small, frequent 5.7.x releases in which the RNTuple work dominates and is often buried below the feature list. Since switching the default write format to RNTuple in 5.7.0, the releases have been about making that path complete: entry bounds and report=True for RNTuple.iterate, GPU interpretation of RNTuple data with nvCOMP decompression, support for the v1.0.1.0 format, and the library kwarg finished. Two of the six releases in this window list no new features at all.
plumber is at 1.3.3, and the last three releases are small: a Swagger redirect fix for hosted environments, a test-robustness change, and Arrow IPC Streams serializers. The feature weight sits further back — 1.3.0 added excel serializers and parsers, ragg and svglite graphics devices, port validation against IANA ranges, and stopped writing parsed bodies to disk.
The pattern across the window is a framework extending what it can exchange rather than what it can do. GeoJSON and parquet in 1.2.0, excel in 1.3.0, Arrow IPC Streams in 1.3.1 — each release adds a format, while routing, OpenAPI and the annotation model stay where 1.1.0 left them. The recent tags suggest that expansion has slowed to hosting-compatibility fixes.
Given three consecutive small releases and no open feature thread in the notes, the next version most likely continues as a maintenance patch rather than adding another serializer family.
Uproot ships small, frequent 5.7.x releases in which the RNTuple work dominates and is often buried below the feature list. Since switching the default write format to RNTuple in 5.7.0, the releases have been about making that path complete: entry bounds and report=True for RNTuple.iterate, GPU interpretation of RNTuple data with nvCOMP decompression, support for the v1.0.1.0 format, and the library kwarg finished. Two of the six releases in this window list no new features at all.
This is a migration project wearing patch-release clothing. The direction is that RNTuple, ROOT's newer columnar format, becomes what Uproot writes and reads by default, with the older TTree path maintained rather than developed. The GPU decompression work points further out: reading physics data straight into accelerator memory rather than staging it through the CPU. Expect the remaining gaps to keep surfacing as bug fixes in the RNTuple path as more of the field writes in the new format.
Continued 5.7.x patches closing RNTuple feature parity with TTree, with the GPU and nvCOMP path the most likely area to gain rather than just get fixed.
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 plumber or uproot5.
stringr keeps trading convenient guesses for predictable errors.
rlang moved tidyeval off R's private internals and onto official C API.
pyjanitor is folding its verbs into pandas groupby objects, one release at a time.
purrr finished a decade of deprecations and picked up a parallel backend.
PyTables opened a path around HDF5's filter pipeline, then chased Python's runtime.
Dask's scheduler spent the year deleting deprecated API, not adding surface.
See all plumber alternatives → · See all uproot5 alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. plumber and uproot5 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. plumber and uproot5 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 DevOps products to evaluate alongside.
Top plumber alternatives in DevOps are ranked by recent ship velocity. Browse the "plumber alternatives" section above for the current picks, or visit /alternatives/plumber for the full list with editorial commentary on each.
Top uproot5 alternatives in DevOps are ranked by recent ship velocity. Browse the "uproot5 alternatives" section above for the current picks, or visit /alternatives/uproot for the full list with editorial commentary on each.