simlandr
Potential landscape tooling settling onto standard R generics after two rounds of renaming.
A side-by-side editorial comparison of quanteda.textmodels and stringx — release velocity, themes, recent moves, and the top alternatives to consider.
Split out of quanteda, then quiet - one new classifier since 2020.
quanteda.textmodels holds the scaling and classification models factored out of quanteda's main package. The visible history is thin: a logistic regression classifier and a native C++ rewrite of svmlin in late 2020, an SVM default change in early 2021, and after that only compatibility work. The most recent release fixes a namespace break caused by quanteda 4.1.0 dropping RcppArmadillo.
A drop-in string API for base R, kept alive by upstream check failures.
stringx reimplements base R's string and date-time functions on top of stringi, aiming for consistent and Unicode-correct behaviour. The visible window holds one behavioural change and five releases that exist because R or stringi moved underneath it. None of the recent notes add capability.
quanteda.textmodels holds the scaling and classification models factored out of quanteda's main package. The visible history is thin: a logistic regression classifier and a native C++ rewrite of svmlin in late 2020, an SVM default change in early 2021, and after that only compatibility work. The most recent release fixes a namespace break caused by quanteda 4.1.0 dropping RcppArmadillo.
The package now moves when its parent or a dependency moves, not on its own schedule. Four of the six most recent releases exist to track changes in quanteda, Matrix, or CRAN policy. The modelling decisions that were made - defaulting textmodel_svm() to the L2-regularized L2-loss dual solver, reducing svmlin to a single algorithm - have not been revisited since.
The next release most likely follows another upstream change in quanteda or a Matrix and Rcpp dependency rather than adding a model.
stringx reimplements base R's string and date-time functions on top of stringi, aiming for consistent and Unicode-correct behaviour. The visible window holds one behavioural change and five releases that exist because R or stringi moved underneath it. None of the recent notes add capability.
The package's shape was settled by 0.2.1 and has not changed since; every release in the past three years is either a check failure fixed or a POSIXxt defect. The one substantive note, 0.2.6, records a behaviour change inherited from stringi rather than chosen here - strptime now fills missing fields from today's midnight. That dependence is the defining fact about the feed.
The next release is most likely another compatibility fix timed to an R or stringi update, since four of the six visible releases were exactly that.
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 quanteda.textmodels or stringx.
Potential landscape tooling settling onto standard R generics after two rounds of renaming.
SEM reporting helpers converging on APA output, one CRAN resubmission at a time.
A raster-to-terra migration is the only readable change in a feed of merge notes.
A nycflights13 generator whose recent work is all about the data being right.
Conditional density and log-likelihood fill out a vine copula regression package.
From a bundled hospital dataset to a live CMS API client.
See all quanteda.textmodels alternatives → · See all stringx alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — r-package, maintenance — within Analytics. quanteda.textmodels and stringx 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. quanteda.textmodels and stringx 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 quanteda.textmodels alternatives in Analytics are ranked by recent ship velocity. Browse the "quanteda.textmodels alternatives" section above for the current picks, or visit /alternatives/quanteda-textmodels for the full list with editorial commentary on each.
Top stringx alternatives in Analytics are ranked by recent ship velocity. Browse the "stringx alternatives" section above for the current picks, or visit /alternatives/stringx for the full list with editorial commentary on each.