simlandr
Potential landscape tooling settling onto standard R generics after two rounds of renaming.
A side-by-side editorial comparison of maths.genealogy and quanteda.textmodels — release velocity, themes, recent moves, and the top alternatives to consider.
A young Mathematics Genealogy client spending its first four releases satisfying CRAN.
maths.genealogy queries the Mathematics Genealogy Project over a WebSocket connection and renders academic advisor-student trees, with plot_grviz() as the visualisation entry point. The package reached CRAN in early 2025 and its functional surface has barely moved since — max_zoom() for deep trees at 0.1.1 is the only user-facing addition in the visible history.
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.
maths.genealogy queries the Mathematics Genealogy Project over a WebSocket connection and renders academic advisor-student trees, with plot_grviz() as the visualisation entry point. The package reached CRAN in early 2025 and its functional surface has barely moved since — max_zoom() for deep trees at 0.1.1 is the only user-facing addition in the visible history.
Every release after the first is CRAN policy management. Three consecutive entries deal with the same underlying problem: examples that hit a live network resource and therefore fail unpredictably on check machines. The progression from wrapping them in \donttest{} to catching a stray case to rewriting all examples against published API-package guidance shows the maintainer converging on a pattern rather than adding features. That is the normal cost of shipping a network client to CRAN, and it appears to be settling.
With the examples problem resolved, the next release is the first plausible opportunity for feature work — likely on the plotting side, given max_zoom() was the sole non-compliance change so far. The entries do not name anything specific in progress.
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.
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 maths.genealogy or quanteda.textmodels.
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.
A drop-in string API for base R, kept alive by upstream check failures.
See all maths.genealogy alternatives → · See all quanteda.textmodels alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — r-package — within Analytics. maths.genealogy and quanteda.textmodels 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. maths.genealogy and quanteda.textmodels 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 maths.genealogy alternatives in Analytics are ranked by recent ship velocity. Browse the "maths.genealogy alternatives" section above for the current picks, or visit /alternatives/maths-genealogy for the full list with editorial commentary on each.
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.