compositional.mle
An MLE package rebuilt around composable solvers, then renamed to match.
A side-by-side editorial comparison of hubData and nabla — release velocity, themes, recent moves, and the top alternatives to consider.
The Arrow data layer for forecast hubs, spending its releases on cloud and materialisation bugs.
hubData is the access layer for hubverse forecasting hubs, connecting to local and cloud-stored model output through Arrow and handing back lazy connections or materialised tibbles. Its releases divide sharply between schema and utility additions in the 1.x line and, more recently, a run of defect fixes in the cloud and Arrow integration. Two of those fixes involved data being silently wrong rather than an error being raised.
nabla dropped its C++ engine to chase exact derivatives at any order.
nabla does forward-mode automatic differentiation in R using dual numbers, returning derivatives exact to machine precision rather than approximated by finite differences. It shipped as dualr in January 2026, then a day later released 0.5.0 under a changed identity: derivatives generalise from a hardcoded second order to arbitrary order through recursive nesting, and the Rcpp and C++ fast paths are deleted so the package is pure R. The current release, 0.7.1, is CRAN resubmission cleanup.
hubData is the access layer for hubverse forecasting hubs, connecting to local and cloud-stored model output through Arrow and handing back lazy connections or materialised tibbles. Its releases divide sharply between schema and utility additions in the 1.x line and, more recently, a run of defect fixes in the cloud and Arrow integration. Two of those fixes involved data being silently wrong rather than an error being raised.
The package has largely finished adding surface and is now paying down the cost of sitting on top of Arrow and S3: ALTREP-backed columns escaping into user sessions, cloud hubs whose declared format differs from what is actually written, and metadata arrays parsing inconsistently. Each fix narrows the gap between what the storage layer does and what an R user expects. The performance-motivated default flip in 2.0.0 points the same way, prioritising large cloud hubs over conservative local behaviour.
Expect continued fixes at the Arrow and cloud boundary, particularly where declared hub configuration and actual stored format disagree, which has now produced defects twice.
nabla does forward-mode automatic differentiation in R using dual numbers, returning derivatives exact to machine precision rather than approximated by finite differences. It shipped as dualr in January 2026, then a day later released 0.5.0 under a changed identity: derivatives generalise from a hardcoded second order to arbitrary order through recursive nesting, and the Rcpp and C++ fast paths are deleted so the package is pure R. The current release, 0.7.1, is CRAN resubmission cleanup.
The 0.5.0 release note states the positioning explicitly: exact machine-precision derivatives at any order, not speed. Removing compiled code to make that claim coherent is an unusual direction, most numerical R packages move the other way, and it commits the package to a niche where correctness beats throughput. The old second-order API survives as deprecated thin wrappers, so the pivot was made without stranding early users. The rapid rename and version jump suggest identity was settled late.
Expect CRAN acceptance to be followed by work on the optimiser and MLE integration paths, where arbitrary-order derivatives have the clearest use.
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 hubData or nabla.
An MLE package rebuilt around composable solvers, then renamed to match.
Eight months from first release to keyring caching and workload identity.
A research-project workflow package where the interesting work is in the plumbing.
A cyclomatic complexity checker that ships once every couple of years, and lands when it does.
Extreme value sampling in pure upkeep mode, mostly answering to Rcpp and CRAN.
A package retired in 2017 just got rewritten against R's public C API.
See all hubData alternatives → · See all nabla alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. hubData and nabla 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. hubData and nabla 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 Analytics products to evaluate alongside.
Top hubData alternatives in Analytics are ranked by recent ship velocity. Browse the "hubData alternatives" section above for the current picks, or visit /alternatives/hubdata for the full list with editorial commentary on each.
Top nabla alternatives in Analytics are ranked by recent ship velocity. Browse the "nabla alternatives" section above for the current picks, or visit /alternatives/nabla for the full list with editorial commentary on each.