HydroPortailStats
France's national flood statistics, ported out of Fortran and into R.
Comparison · Infra & APIs
IsoriX vs mize
A side-by-side editorial comparison of IsoriX and mize — release velocity, themes, recent moves, and the top alternatives to consider.
Shared themes:r-package
IsoriX vs mize: at a glance
What is IsoriX?
An isotope geolocation package still recovering from the r-spatial retirement
IsoriX builds isoscapes and assigns organisms to geographic origin from stable isotope data. Its recent history is defined by the October 2023 retirement of the old R spatial stack: version 0.9.1 recoded substantial parts of the package to drop raster and sp, 0.9.2 restored capabilities that migration had broken - saving and reloading IsoriX objects, and plotting ocean masks containing holes - and documented the new plotting calls that replace the old sp.polygons and sp.points idioms. Since then 0.9.3 revised the bundled bat calibration datasets and 0.9.4 moved the documentation off bookdown.org.
What is mize?
A numerical optimization toolkit that has been feature-complete and quiet since 2017
mize provides a configurable interface to unconstrained numerical optimization methods - line searches, gradient descent variants, quasi-Newton updates - usable both as a one-shot call and as a stepwise iterator. Its functional surface has not changed since the initial CRAN release in July 2017. Every release since has been a patch: R-devel compatibility, line search edge cases, and in 2026's 0.2.5 the removal of LazyData from DESCRIPTION plus deletion of some flaky tests.
IsoriX vs mize: editorial side-by-side
IsoriX
0.0INFRA · APIS
An isotope geolocation package still recovering from the r-spatial retirement
◆ Current state
IsoriX builds isoscapes and assigns organisms to geographic origin from stable isotope data. Its recent history is defined by the October 2023 retirement of the old R spatial stack: version 0.9.1 recoded substantial parts of the package to drop raster and sp, 0.9.2 restored capabilities that migration had broken - saving and reloading IsoriX objects, and plotting ocean masks containing holes - and documented the new plotting calls that replace the old sp.polygons and sp.points idioms. Since then 0.9.3 revised the bundled bat calibration datasets and 0.9.4 moved the documentation off bookdown.org.
◆ Where it's heading
Two years of the visible history have gone on infrastructure the science did not ask for. The 0.9.1 notes are unusually candid, warning users that the surrounding package landscape was still in flux and that incompatibility bugs were likely to keep surfacing, which 0.9.2 then confirmed. Only in 0.9.3 does domain work reappear: the bat fur isotope values in the calibration and assignment datasets were corrected to align with current keratin reference material normalisation, so results computed against the old datasets are not comparable with new ones.
◆ Prediction
With the spatial migration settled and the documentation rehomed, the next release is more likely to return to isoscape functionality than to infrastructure, though the entries do not name a specific feature.
mize
0.0INFRA · APIS
A numerical optimization toolkit that has been feature-complete and quiet since 2017
◆ Current state
mize provides a configurable interface to unconstrained numerical optimization methods - line searches, gradient descent variants, quasi-Newton updates - usable both as a one-shot call and as a stepwise iterator. Its functional surface has not changed since the initial CRAN release in July 2017. Every release since has been a patch: R-devel compatibility, line search edge cases, and in 2026's 0.2.5 the removal of LazyData from DESCRIPTION plus deletion of some flaky tests.
◆ Where it's heading
The pattern is a stable library rather than an abandoned one. Fixes address real reports - a bracket_step error when the Schmidt line search exhausts its function evaluation budget, an incorrect gradient count under backtracking with a specified step_down - and the maintainer used one release note to clarify that backtracking behaviour differs depending on whether step_down is supplied, which reads as answering a recurring question. The five and a half year gap between 0.2.4 and 0.2.5 is the clearest signal: the package is maintained on demand, not developed.
◆ Prediction
Expect nothing until an R or CRAN policy change forces another compliance patch, which is what triggered the most recent release.
Alternatives to IsoriX and mize
Other Infra & APIs 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 IsoriX or mize.
bsvarSIGNs
Sign, zero and narrative restrictions brought into the bsvars ecosystem.
estimatr
Fast design-based estimators for experiments, coasting on CRAN patches.
ggdist
The grammar of uncertainty visualization, now drawing the uncertainty in its own estimates.
ipaddress
IP address vectors for R that hit 1.0 and then went quiet.
ltertools
A column-key toolkit for stitching decades of ecological field data into one table.
Recent activity from IsoriX and mize
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 6mo agomizeCRAN compliance patch after five years of silence
- 7mo agoIsoriXDocumentation rehomed after bookdown.org shutdown
- 1y agoIsoriXCalibration datasets corrected to current keratin reference standards
- 2y agoIsoriXSaving objects and masked plotting restored after the spatial migration
- 2y agoIsoriXv0.9.1.9999
- 2y agoIsoriXPackage recoded to drop the retiring spatial dependencies
- 5y agoIsoriXCRAN release version 0.5
- 5y agomizeBacktracking line search reporting and documentation fix
- 6y agomizeR-devel compatibility fix for class checking
- 7y agomizeSchmidt line search error when the evaluation budget is exhausted
- 7y agomizeStage check fix for bold driver and backtracking
- 9y agomizeCRAN release 0.1.1
Frequently asked questions
What is the difference between IsoriX and mize?
Both compete on the same themes — r-package — within Infra & APIs. IsoriX and mize 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.
Is IsoriX better than mize?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. IsoriX and mize 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 Infra & APIs products to evaluate alongside.
What are the best alternatives to IsoriX?
Top IsoriX alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "IsoriX alternatives" section above for the current picks, or visit /alternatives/isorix for the full list with editorial commentary on each.
What are the best alternatives to mize?
Top mize alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "mize alternatives" section above for the current picks, or visit /alternatives/mize for the full list with editorial commentary on each.