tfevents
tfevents logs TensorBoard events from R, and this release only changes who maintains it.
Comparison · ai-assistants
mlr3hyperband vs ONNX Runtime
A side-by-side editorial comparison of mlr3hyperband and ONNX Runtime — release velocity, themes, recent moves, and the top alternatives to consider.
mlr3hyperband vs ONNX Runtime: at a glance
What is mlr3hyperband?
Hyperband tuning for mlr3, now built on an asynchronous backend it treats as mandatory
mlr3hyperband supplies successive-halving and Hyperband optimizers to the mlr3 tuning stack. Its recent releases are dominated by ecosystem plumbing rather than new search algorithms: a hard floor of `rush` 1.0.0, alignment with mlr3 1.7.2, and a move onto the ecosystem's new base logger. The last genuinely new optimizer was `OptimizerAsyncSuccessiveHalving` in 1.0.0.
What is ONNX Runtime?
ONNX Runtime is retiring WebGL for WebGPU and turning on telemetry outside Windows.
v1.29.0 announces the deprecation of WebGL and JSEP in onnxruntime-web, naming the native WebGPU execution provider as the path forward, and adds POSIX telemetry on Linux, macOS, Android and iOS for telemetry-enabled builds, disabled via ORT_DISABLE_TELEMETRY. It also carries a long list of security fixes — a TensorRT path-traversal vulnerability, plus rank, shape and bounds validation across a dozen kernels. Separately, the WebGPU plug-in reached v0.2.1 with fused FlashAttention decode kernels for any sequence length and Qwen3 and Gemma 4 model paths, while v1.28.0 made cuDNN and cuFFT optional at runtime to shrink the CUDA redistributable.
mlr3hyperband vs ONNX Runtime: editorial side-by-side
mlr3hyperband
2.5AI-ASSISTANTS
Hyperband tuning for mlr3, now built on an asynchronous backend it treats as mandatory
◆ Current state
mlr3hyperband supplies successive-halving and Hyperband optimizers to the mlr3 tuning stack. Its recent releases are dominated by ecosystem plumbing rather than new search algorithms: a hard floor of `rush` 1.0.0, alignment with mlr3 1.7.2, and a move onto the ecosystem's new base logger. The last genuinely new optimizer was `OptimizerAsyncSuccessiveHalving` in 1.0.0.
◆ Where it's heading
The package has finished a transition from synchronous tuning to a distributed one and is now consolidating it. 1.1.1 raised the `rush` minimum to 1.0.0 and deleted every compatibility workaround for older versions, which ends the period where the async backend was optional. Logging moved the same way in 1.1.0: `bbotk`, `mlr3tuning` and `mlr3hyperband` now log through a child of a shared `mlr3` logger rather than their own.
◆ Prediction
With the compatibility layer gone, the next release is more likely to extend async optimizers than to revisit the backend, since the recent versions spent their changes on removing optionality rather than adding surface. The entries give no signal on which optimizer comes next.
ONNX Runtime
6.3AI-ASSISTANTS
ONNX Runtime is retiring WebGL for WebGPU and turning on telemetry outside Windows.
◆ Current state
v1.29.0 announces the deprecation of WebGL and JSEP in onnxruntime-web, naming the native WebGPU execution provider as the path forward, and adds POSIX telemetry on Linux, macOS, Android and iOS for telemetry-enabled builds, disabled via ORT_DISABLE_TELEMETRY. It also carries a long list of security fixes — a TensorRT path-traversal vulnerability, plus rank, shape and bounds validation across a dozen kernels. Separately, the WebGPU plug-in reached v0.2.1 with fused FlashAttention decode kernels for any sequence length and Qwen3 and Gemma 4 model paths, while v1.28.0 made cuDNN and cuFFT optional at runtime to shrink the CUDA redistributable.
◆ Where it's heading
The browser story is consolidating onto one backend after years of maintaining three, and the WebGPU plug-in's independent release track is what made that credible — the attention work landed there first. On the core runtime the direction is subtraction: fewer linked CUDA libraries, removed TensorRT fused kernels, a deprecated CUDA 12, and a steady stream of input-validation hardening that suggests sustained security review. Note the feed is non-monotonic, with v1.26.0 and v1.29.0 published minutes apart.
◆ Prediction
CUDA 12 removal in 1.27.0 was already announced, and the CUDA runtime is slated to move into a dedicated execution provider — that separation is the next structural change to watch.
Alternatives to mlr3hyperband and ONNX Runtime
Other ai-assistants 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 mlr3hyperband or ONNX Runtime.
safetensors
safetensors for R changes hands with no code change to show for it.
torchdatasets
torchdatasets ships custodial work as mlverse gathers its torch satellites under one maintainer.
mlr3tuningspaces
A curated catalogue of published hyperparameter search spaces, now reaching deep neural networks
LibreChat
LibreChat's agents stop being fire-and-forget: you can now interrupt, steer, and answer them mid-run.
Ollama
Ollama now ships on the model release calendar, with an MLX build attached to each drop.
See all mlr3hyperband alternatives → · See all ONNX Runtime alternatives →
Recent activity from mlr3hyperband and ONNX Runtime
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 3d agoONNX RuntimeONNX Runtime 1.29 deprecates WebGL and JSEP, adds POSIX telemetry ⚡
- 3d agoONNX RuntimeONNX Runtime 1.26 adds RISC-V vector support and .ort memory mapping
- 16d agoONNX RuntimeWebGPU plug-in: FlashAttention fusions, Qwen3 and Gemma 4 paths
- 21d agomlr3hyperbandrush 1.0.0 required; old compatibility paths removed
- 21d agoONNX RuntimeONNX 1.22 upgrade, slimmer CUDA footprint, experimental C API
- 1mo agoONNX RuntimePatch release: QMoE batch-1 decode fast path and fixes
- 1mo agoONNX RuntimeSecurity-hardening minor targeting ONNX 1.21
- 5mo agomlr3hyperbandLogging reparented under a shared mlr3 base logger
- 1y agomlr3hyperbandAsync successive halving lands in 1.0.0 ⚡
- 2y agomlr3hyperbandCompatibility with bbotk and mlr3tuning 1.0.0
- 2y agomlr3hyperbandCompatibility with paradox 1.0.0
- 3y agomlr3hyperbandUnloading now clears registered optimizers
Frequently asked questions
What is the difference between mlr3hyperband and ONNX Runtime?
They serve adjacent needs but don't currently overlap on shipped themes. ONNX Runtime is currently shipping more aggressively (velocity 6.3 vs 2.5), with 1 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.
Is mlr3hyperband better than ONNX Runtime?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. ONNX Runtime is currently shipping more aggressively (velocity 6.3 vs 2.5), with 1 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other ai-assistants products to evaluate alongside.
What are the best alternatives to mlr3hyperband?
Top mlr3hyperband alternatives in ai-assistants are ranked by recent ship velocity. Browse the "mlr3hyperband alternatives" section above for the current picks, or visit /alternatives/mlr3hyperband for the full list with editorial commentary on each.
What are the best alternatives to ONNX Runtime?
Top ONNX Runtime alternatives in ai-assistants are ranked by recent ship velocity. Browse the "ONNX Runtime alternatives" section above for the current picks, or visit /alternatives/onnx-runtime for the full list with editorial commentary on each.