mlr3misc
The mlr3 utility belt has spent a year rebuilding how errors travel
A side-by-side editorial comparison of ps and wk — release velocity, themes, recent moves, and the top alternatives to consider.
ps grew from a process inspector into the thing that reliably kills what you started.
ps is the cross-platform process API underneath processx and callr, and its recent work splits between widening what it can query and hardening the guarantee that a handle still refers to the process you think it does. Version 1.8.0 added interruptible multi-process waiting, vectorised signalling, and graceful kill with a TERM-then-KILL grace period. Version 1.9.3 rebuilt Linux process creation times on a clock pair instead of integer-second boot time, closing a window where two processes could look identical.
wk spent one release fixing what empty means, then went quiet.
wk provides the lightweight geometry vectors and streaming handler interface that sit underneath sf and the rest of R's geospatial stack. The 0.7 and 0.8 lines built out the surface — PROJJSON CRS lookup, ring winding, coordinate replacement functions, hex conversion — and 0.9.0 landed breaking changes to how empty and null points are represented. The three releases since are entirely reactive: compile under STRICT_R_HEADERS, fix format strings for R-devel, pass tests against a new sf.
ps is the cross-platform process API underneath processx and callr, and its recent work splits between widening what it can query and hardening the guarantee that a handle still refers to the process you think it does. Version 1.8.0 added interruptible multi-process waiting, vectorised signalling, and graceful kill with a TERM-then-KILL grace period. Version 1.9.3 rebuilt Linux process creation times on a clock pair instead of integer-second boot time, closing a window where two processes could look identical.
The direction is from observation to control. Early releases in view are per-process queries — CPU times, memory, affinity — and the newer ones are orchestration: wait on many processes with a timeout, signal a list of handles at once, terminate a tree politely before forcing it. The create-time precision work is what makes that safe, since a handle's identity is a PID plus a start time, and a one-second resolution start time is not enough to rule out PID reuse on a busy machine.
Expect the remaining platform-specific gaps in ps_status() and ps_apps() to close before any new capability area opens, since the recent additions have all been driven by processx issue reports.
wk provides the lightweight geometry vectors and streaming handler interface that sit underneath sf and the rest of R's geospatial stack. The 0.7 and 0.8 lines built out the surface — PROJJSON CRS lookup, ring winding, coordinate replacement functions, hex conversion — and 0.9.0 landed breaking changes to how empty and null points are represented. The three releases since are entirely reactive: compile under STRICT_R_HEADERS, fix format strings for R-devel, pass tests against a new sf.
This looks like a foundation package that has reached the shape it wanted. Feature work stopped after 0.9.2 and what remains is upkeep triggered by R-devel, compiler flags and sf releases — maintenance defined by other people's changes, which for a dependency this low in the stack is a reasonable end state rather than neglect. The unresolved question is whether anything still drives it forward now that the empty-geometry semantics are settled.
The entries do not support a confident prediction of new features; on this evidence the next release is most likely another compatibility fix prompted by sf or R-devel.
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 ps or wk.
The mlr3 utility belt has spent a year rebuilding how errors travel
Zed ships weekly, and the Git surface is finally catching up to the agent surface
odbc keeps turning into an authentication broker with a database driver attached.
Load-bearing across CRAN, and untouched since January 2021.
A package whose entire job is to ship someone else's database on time.
TinyTeX went where the containers are: Alpine, ARM64, and a naming scheme to match.
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. ps and wk 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. ps and wk 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 ps alternatives in DevOps are ranked by recent ship velocity. Browse the "ps alternatives" section above for the current picks, or visit /alternatives/ps-r for the full list with editorial commentary on each.
Top wk alternatives in DevOps are ranked by recent ship velocity. Browse the "wk alternatives" section above for the current picks, or visit /alternatives/wk-r for the full list with editorial commentary on each.