easystats
The easystats meta-package is install tooling wrapped around a relicensed ecosystem.
A side-by-side editorial comparison of discrim and tune — release velocity, themes, recent moves, and the top alternatives to consider.
discrim settled into a thin engine shim after handing its model definitions to parsnip.
discrim is the parsnip extension for discriminant analysis, exposing linear, quadratic, flexible and regularized variants through the tidymodels interface. Its model definition functions moved into parsnip itself in 0.2.0, leaving this package as the engine and prediction layer. The two most recent releases are a documentation fix and a single prediction bug.
tune extends tuning past the model itself to postprocessors, and adds a second parallel backend
tune runs hyperparameter search for tidymodels. Version 2.0.0 rewrote tune_grid() to make postprocessing tunable alongside preprocessing and the model, changed the .config naming scheme to match, and added mirai as a parallel backend next to future. Version 2.1.0 followed with quantile regression support and a replacement Gaussian process engine.
discrim is the parsnip extension for discriminant analysis, exposing linear, quadratic, flexible and regularized variants through the tidymodels interface. Its model definition functions moved into parsnip itself in 0.2.0, leaving this package as the engine and prediction layer. The two most recent releases are a documentation fix and a single prediction bug.
The package built out method coverage early, adding quadratic discriminant analysis in 0.1.2, the sda and sparsediscrim engines in 0.1.3 and case weights in 1.0.0, then stopped growing. Handing definitions upstream to parsnip in 0.2.0 confirmed the shape: discrim is where engines are wired, not where the API lives. Cadence since 2022 is roughly one small fix a year.
Nothing in the entries points to new methods or engines; the next release is most likely another CRAN or prediction-path fix.
tune runs hyperparameter search for tidymodels. Version 2.0.0 rewrote tune_grid() to make postprocessing tunable alongside preprocessing and the model, changed the .config naming scheme to match, and added mirai as a parallel backend next to future. Version 2.1.0 followed with quantile regression support and a replacement Gaussian process engine.
Two migrations run through this timeline. The tunable surface keeps widening - first censored regression as a mode, then postprocessors via tailor - so that a candidate is now a preprocessor, model and postprocessor triple rather than just a model. The parallel story has moved from foreach to future and now to mirai, each step deprecating the last. Neither is finished.
Expect the foreach path to be removed outright, and the postprocessing surface to grow as tailor gains more steps; the GauPro switch will likely need follow-up as its behavior differs from the old engine.
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 discrim or tune.
The easystats meta-package is install tooling wrapped around a relicensed ecosystem.
dbparser shed its database and CSV writers to become just a DrugBank parser.
desirability2 is making multi-metric model selection a first-class tidymodels step.
crosstalk is frozen infrastructure: four releases in five years, mostly CRAN upkeep.
cmdstanr keeps adding fast approximations beside full HMC, and fighting Windows toolchains.
comtradr's 1.0 line is a long tail of patches against a brittle UN trade API.
See all discrim alternatives → · See all tune alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — tidymodels — within Analytics. discrim and tune 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. discrim and tune 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 discrim alternatives in Analytics are ranked by recent ship velocity. Browse the "discrim alternatives" section above for the current picks, or visit /alternatives/discrim for the full list with editorial commentary on each.
Top tune alternatives in Analytics are ranked by recent ship velocity. Browse the "tune alternatives" section above for the current picks, or visit /alternatives/tune for the full list with editorial commentary on each.