mice
mice can finally predict, not just estimate, from multiply imputed data.
A side-by-side editorial comparison of qol and selection.index — release velocity, themes, recent moves, and the top alternatives to consider.
A SAS-to-R comfort layer that has quietly grown into its own dialect.
qol is a one-maintainer R package aimed at analysts moving from SAS: SAS-shaped verbs (compute., if./else_if., retain_value, do_if blocks), format-driven tabulation through any_table()/summarise_plus(), and styled Excel output as the default destination. Releases land roughly monthly and each one is large. The recent line has shifted from adding verbs to letting conditions be written as parsed character strings, which is the closest the package gets to reproducing SAS syntax inside R.
A dormant plant-breeding package returns as a genomic selection index suite
selection.index computes selection indices for plant breeding — weighting several traits into one number breeders can rank on. After two years of silence it shipped 2.0.0 in March 2026, and the package is barely recognisable: snake_case throughout, an Rcpp and RcppEigen computational core, and index families for genomic data, marker data, multi-stage trials and constrained genetic gain sitting beside the original phenotypic ones.
qol is a one-maintainer R package aimed at analysts moving from SAS: SAS-shaped verbs (compute., if./else_if., retain_value, do_if blocks), format-driven tabulation through any_table()/summarise_plus(), and styled Excel output as the default destination. Releases land roughly monthly and each one is large. The recent line has shifted from adding verbs to letting conditions be written as parsed character strings, which is the closest the package gets to reproducing SAS syntax inside R.
Three threads are visible across these releases. Syntax fidelity is the newest: ifelse_multi() introduced character-string conditions with SAS-style writing, and if./else_if. immediately picked the style up. Tabulation flexibility is the constant — any_table() gains per-variable statistic selection, nested variable combinations in brackets, vector order_by, compute support. The third is ecosystem plumbing the maintainer builds when a gap appears: file I/O in 1.3.0, a console message system, global style options, macro variables, and in 1.3.2 a code_statistics() script scanner. Renames to dodge data.table and dplyr masking recur often enough to be a pattern.
The maintainer flagged the new percentile behaviour as a first iteration that only works with few grouping variables, so a performance pass on it is the clearest outstanding item. Beyond that the character-condition syntax has reached three functions in two releases and looks likely to spread to the remaining filter-bearing verbs.
selection.index computes selection indices for plant breeding — weighting several traits into one number breeders can rank on. After two years of silence it shipped 2.0.0 in March 2026, and the package is barely recognisable: snake_case throughout, an Rcpp and RcppEigen computational core, and index families for genomic data, marker data, multi-stage trials and constrained genetic gain sitting beside the original phenotypic ones.
The first version series added one function at a time — combinatorial indices, then genetic advance, then mean performance under randomised block designs — against a fixed phenotypic framing. Version 2.0.0 abandons that framing rather than extending it. Genomic and marker information become inputs the package understands, multi-cycle simulation becomes a built-in toolset, and the old combinatorial entry points are replaced by a named lpsi(). The 2.0.1 follow-up is entirely CI and numerical-stability work, which reads like a maintainer bracing a much larger surface.
A seventeen-runner CI matrix mirroring every CRAN check flavour, added days after 2.0.0, says the immediate concern is keeping a compiled multi-family package green rather than adding to it. Expect stabilisation releases before anything new.
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 qol or selection.index.
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 qol alternatives → · See all selection.index alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. qol and selection.index 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. qol and selection.index 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 qol alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "qol alternatives" section above for the current picks, or visit /alternatives/qol for the full list with editorial commentary on each.
Top selection.index alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "selection.index alternatives" section above for the current picks, or visit /alternatives/selection-index for the full list with editorial commentary on each.