metatools
SDTM supplemental-qualifier merging got sturdier, then the package went quiet for two years.
A side-by-side editorial comparison of mlr3extralearners and nanonext — release velocity, themes, recent moves, and the top alternatives to consider.
The mlr3 learner catalogue is growing fast and pruning hyperparameters just as deliberately.
mlr3extralearners is the overflow catalogue for mlr3 learners that do not ship in the core packages — currently spanning H2O, Botorch, fastai, glmnet, survival and competing-risks models. The last two feature releases added roughly thirty learners between them. 1.6.0 then went the other way, cutting hyperparameters that were never correctly forwarded.
nanonext keeps shrinking its build requirements while adding messaging primitives.
The R binding to NNG ships roughly monthly. Since February the package added an HTTP server that can run synchronously or through the later event loop, a zero-copy device forwarder for building brokers and proxies, and support for pthread-enabled WebAssembly targets. Send operations now move the buffer straight into the NNG message, halving peak memory on serialized sends.
mlr3extralearners is the overflow catalogue for mlr3 learners that do not ship in the core packages — currently spanning H2O, Botorch, fastai, glmnet, survival and competing-risks models. The last two feature releases added roughly thirty learners between them. 1.6.0 then went the other way, cutting hyperparameters that were never correctly forwarded.
Two forces are visible. The catalogue expands in bursts — 1.4.0 and 1.5.0 each added large batches, including a full H2O family and Bayesian regression models — while the maintenance releases in between are dominated by skipping tests on platforms where Python-backed learners crash. 1.6.0 marks a shift toward correctness of the existing surface: priority_lasso parameter sets reduced to what actually passes through, and Cox-inapplicable glmnet parameters removed.
The Python-backed learners are the recurring source of platform instability, so expect continued pinning and test-skipping there alongside the next batch of additions.
The R binding to NNG ships roughly monthly. Since February the package added an HTTP server that can run synchronously or through the later event loop, a zero-copy device forwarder for building brokers and proxies, and support for pthread-enabled WebAssembly targets. Send operations now move the buffer straight into the NNG message, halving peak memory on serialized sends.
Two directions run in parallel. One is making the package installable anywhere — the build-time cmake dependency is gone, so compiling bundled NNG and Mbed TLS needs only a C compiler, and WebAssembly targets are supported. The other is raising the ceiling on what can be built on top: device_aio() for message forwarding, an HTTP and WebSocket server with a content map, and stream buffer control. Bug fixes in recent releases concentrate on memory safety in the bundled C sources.
Given the pace and the tight coupling declared in each release, expect the next version to track a mirai requirement and continue hardening the HTTP server paths that the last two releases have been leaking memory in.
Other Analytics 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 mlr3extralearners or nanonext.
SDTM supplemental-qualifier merging got sturdier, then the package went quiet for two years.
marquee is filling in the typographic details — outlines, border types, real font metrics for underlines.
A clinical-script logger that stopped shipping after its 0.2 line, changelogs made of merged PRs.
R's object inspector is losing its view of the internals as CRAN closes off the private C API.
A weather-station data client that broke one return type to hand back distances instead of bare IDs.
giscoR's 1.0 moved its dataset index into the cache, so new Eurostat releases arrive without a package update.
See all mlr3extralearners alternatives → · See all nanonext alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. nanonext is currently shipping more aggressively (velocity 2.5 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. nanonext is currently shipping more aggressively (velocity 2.5 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 Analytics products to evaluate alongside.
Top mlr3extralearners alternatives in Analytics are ranked by recent ship velocity. Browse the "mlr3extralearners alternatives" section above for the current picks, or visit /alternatives/mlr3extralearners for the full list with editorial commentary on each.
Top nanonext alternatives in Analytics are ranked by recent ship velocity. Browse the "nanonext alternatives" section above for the current picks, or visit /alternatives/nanonext for the full list with editorial commentary on each.