mice
mice can finally predict, not just estimate, from multiply imputed data.
A side-by-side editorial comparison of lares and writeAlizer — release velocity, themes, recent moves, and the top alternatives to consider.
One analyst's toolbox, still shipping: Meta MMM tooling beside Wordle solvers
lares is Bernardo Lares' personal R sidekick and has never pretended otherwise — the same release adds a marketing-mix diagnostic and a function to keep your screen awake. The serious core is the Robyn/Meta arm: model selection, per-channel performance decomposition, cross-channel budget allocation. Around it sit h2o AutoML wrappers, credential and cache helpers, MP3 tagging, and a family of games.
Six months of releases and not one of them touched the scoring models
writeAlizer generates predicted writing-quality scores from features produced by Coh-Metrix, ReaderBench and GAMET, downloading its trained scoring models on demand. Every release in this window — nine of them between September 2025 and February 2026 — is about that download path rather than the scoring: classed error conditions, checksum verification, an offline mode, a mockable artifact directory, and dependency reporting for the model families a user actually invokes.
lares is Bernardo Lares' personal R sidekick and has never pretended otherwise — the same release adds a marketing-mix diagnostic and a function to keep your screen awake. The serious core is the Robyn/Meta arm: model selection, per-channel performance decomposition, cross-channel budget allocation. Around it sit h2o AutoML wrappers, credential and cache helpers, MP3 tagging, and a family of games.
Over two years the Robyn tooling matured first — robyn_performance() and robyn_modelselector() were rebuilt release after release through 2024 — and recent work has drifted outward into media and API plumbing: encrypted file helpers in 5.3.2, then an iTunes-first metadata path, MP3 tag writing, and a move of holidays() onto the Nager.Date API in 5.4.0. Cadence is roughly quarterly and the package has been quiet for three months.
The pattern in nearly every release is that a third-party API moves and lares follows it — Meta's version bumps, Robyn 3.12.0, now Nager.Date. Expect the next release to be another compatibility pass plus whatever utility the author needed that week; nothing in these entries points at a structural change.
writeAlizer generates predicted writing-quality scores from features produced by Coh-Metrix, ReaderBench and GAMET, downloading its trained scoring models on demand. Every release in this window — nine of them between September 2025 and February 2026 — is about that download path rather than the scoring: classed error conditions, checksum verification, an offline mode, a mockable artifact directory, and dependency reporting for the model families a user actually invokes.
The package is being made safe to distribute. CRAN's policy on packages that reach the internet drove the first wave — graceful failure, tests that preflight their URLs and skip, examples seeded from a local mock model — and 1.7.0 turned the accumulated fixes into structure with named error classes for each failure mode. Only 1.7.2 adds anything a user would ask for: filename handling for Coh-Metrix and GAMET outputs that arrive as paths.
With the artifact registry hardened and documented, the pressure that produced nine releases in six months should ease, and attention can return to the models themselves — the vignette on scoring-model development added in 1.7.2 hints at that. Nothing here promises new models.
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 lares or writeAlizer.
mice can finally predict, not just estimate, from multiply imputed data.
A market-microstructure toolkit that keeps adding estimators as the papers land.
A vowel-analysis package trimming dependencies after an email address got it archived.
The R half of the EMU speech database system, fixing what was quietly broken.
A Bayesian model-averaging package spending its 2.0 on memory, not methods.
tidyplots keeps rebuilding its own foundations rather than layering around them.
See all lares alternatives → · See all writeAlizer alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. lares and writeAlizer 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. lares and writeAlizer 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.
Top lares alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "lares alternatives" section above for the current picks, or visit /alternatives/lares for the full list with editorial commentary on each.
Top writeAlizer alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "writeAlizer alternatives" section above for the current picks, or visit /alternatives/writealizer for the full list with editorial commentary on each.