gutenbergr
gutenbergr has been rebuilt around caching and mirror resilience
Comparison · Analytics
discrim vs dtplyr
A side-by-side editorial comparison of discrim and dtplyr — release velocity, themes, recent moves, and the top alternatives to consider.
discrim vs dtplyr: at a glance
What is discrim?
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.
What is dtplyr?
dtplyr stopped hijacking data.table objects and became an opt-in translator
dtplyr converts dplyr and tidyr code into data.table syntax, and 1.3.0 redrew its boundary: verbs no longer dispatch to dtplyr translations just because dtplyr is loaded, so lazy_dt() has to be called explicitly. Since then the work has been translation coverage — reframe(), case_match(), consecutive_id() — plus a long tail of correctness fixes in grouping and .by.
discrim vs dtplyr: editorial side-by-side
discrim
0.0ANALYTICS
discrim settled into a thin engine shim after handing its model definitions to parsnip.
◆ Current state
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.
◆ Where it's heading
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.
◆ Prediction
Nothing in the entries points to new methods or engines; the next release is most likely another CRAN or prediction-path fix.
dtplyr
0.0ANALYTICS
dtplyr stopped hijacking data.table objects and became an opt-in translator
◆ Current state
dtplyr converts dplyr and tidyr code into data.table syntax, and 1.3.0 redrew its boundary: verbs no longer dispatch to dtplyr translations just because dtplyr is loaded, so lazy_dt() has to be called explicitly. Since then the work has been translation coverage — reframe(), case_match(), consecutive_id() — plus a long tail of correctness fixes in grouping and .by.
◆ Where it's heading
The package is trailing dplyr's own feature releases rather than leading them, adding each new verb once it settles upstream. Performance work is targeted at specific verbs where data.table has a faster primitive: setorder() for arrange(), reference drops for select(), rleid() for consecutive_id(). Release cadence has thinned considerably since 2023.
◆ Prediction
Expect further one-for-one translations as dplyr adds verbs, and continued fixes around .by and non-standard column names; the entries show no sign of a broader redesign.
Alternatives to discrim and dtplyr
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 dtplyr.
ggspatial
ggspatial finishes its move off raster and onto terra
ggraph
ggraph has settled into ggplot2 compatibility duty
feasts
feasts is splitting itself in two, moving every plot into ggtime
gganimate
gganimate is in caretaker mode, tracking ggplot2 and little else
fable
fable keeps widening its model shelf, one econometric class at a time
See all discrim alternatives → · See all dtplyr alternatives →
Recent activity from discrim and dtplyr
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 8mo agodiscrimFix for FDA models failing at prediction time
- 11mo agodtplyrreframe(), case_match() and consecutive_id() gain translations
- 11mo agodiscrimDocumentation links updated to stay on CRAN
- 3y agodtplyrcrayon dependency dropped
- 3y agodtplyrVerbs stop auto-dispatching; lazy_dt() now required ⚡
- 3y agodtplyrdtplyr 1.2.2
- 4y agodiscrimCase weights enabled for flexible and linear discriminant models
- 4y agodiscrimModel definitions moved upstream into parsnip
- 4y agodtplyrdtplyr 1.2.1
- 4y agodtplyrEight tidyr verbs gain data.table translations
- 5y agodiscrimsda and sparsediscrim engines added for LDA and QDA
- 5y agodiscrimdiscrim_quad() added; package relicensed to MIT ⚡
Frequently asked questions
What is the difference between discrim and dtplyr?
They serve adjacent needs but don't currently overlap on shipped themes. discrim and dtplyr 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 discrim better than dtplyr?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. discrim and dtplyr 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.
What are the best alternatives to discrim?
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.
What are the best alternatives to dtplyr?
Top dtplyr alternatives in Analytics are ranked by recent ship velocity. Browse the "dtplyr alternatives" section above for the current picks, or visit /alternatives/dtplyr for the full list with editorial commentary on each.