← Back to home
Comparison · Analytics

fastglm vs quanteda

A side-by-side editorial comparison of fastglm and quanteda — release velocity, themes, recent moves, and the top alternatives to consider.

Shared themes:r-package

fastglm vs quanteda: at a glance

Featurefastglmquanteda
SectorAnalyticsAnalytics
Velocity score0.02.5
Sparks · 30d00
Top themesstatistical-computing, generalized-linear-models, cpp, r-packagetext-analysis, natural-language-processing, r-package, torch
Last editorial update2h ago2h ago
WebsiteVisit →Visit →

What is fastglm?

A fast GLM solver stops being one function and becomes a count-model family

fastglm ran C++ IRLS for standard generalized linear models for six years with almost no releases. In May 2026 it added three top-level model types — negative binomial with jointly estimated dispersion, hurdle, and zero-inflated — each with the entire fitting driver in C++ rather than an R loop around a C++ kernel. The following release generalised Firth bias reduction to every standard family across dense, sparse and streaming backends.

Read the full fastglm trajectory →

What is quanteda?

Text analysis in R keeps optimising its token internals — and builds a path out to torch

quanteda is a mature framework for quantitative text analysis in R. Since the 4.0 rewrite around external-pointer tokens objects, releases have concentrated on the internals: recompilation control, memory reduction on concatenation, type-table consistency between tokens and dfm objects. The newest release adds tokens_recompile() for explicit ID reassignment, stops query functions from recompiling implicitly, and returns dense rather than sparse tensors from as.tensor() with arguments passed through to torch.

Read the full quanteda trajectory →

fastglm vs quanteda: editorial side-by-side

F
fastglm
ANALYTICS
0.0

A fast GLM solver stops being one function and becomes a count-model family

◆ Current state

fastglm ran C++ IRLS for standard generalized linear models for six years with almost no releases. In May 2026 it added three top-level model types — negative binomial with jointly estimated dispersion, hurdle, and zero-inflated — each with the entire fitting driver in C++ rather than an R loop around a C++ kernel. The following release generalised Firth bias reduction to every standard family across dense, sparse and streaming backends.

◆ Where it's heading

The package changed what it is. Through 0.0.3 it was a drop-in replacement for glm() competing on speed; from 0.1.0 it targets the models people leave base R for — MASS::glm.nb, pscl::hurdle, pscl::zeroinfl — and reimplements their full estimation loops natively. The 0.1.1 follow-up is consolidation on that new surface: Firth generalised past binomial logit, SQUAREM acceleration on the zero-inflation EM driver, and a run of clamping guards and initialization fixes on the families most prone to overflow.

◆ Prediction

The numerical-stability work in 0.1.1 clusters on Tweedie and the inverse and sqrt link families, which suggests those paths are the newest and least exercised — expect further correctness fixes there before new model types.

Q
quanteda
ANALYTICS
2.5

Text analysis in R keeps optimising its token internals — and builds a path out to torch

◆ Current state

quanteda is a mature framework for quantitative text analysis in R. Since the 4.0 rewrite around external-pointer tokens objects, releases have concentrated on the internals: recompilation control, memory reduction on concatenation, type-table consistency between tokens and dfm objects. The newest release adds tokens_recompile() for explicit ID reassignment, stops query functions from recompiling implicitly, and returns dense rather than sparse tensors from as.tensor() with arguments passed through to torch.

◆ Where it's heading

Two threads run in parallel. The dominant one is performance and correctness housekeeping on the tokens_xptr representation introduced in 4.0 — each release closes another case where the external-pointer path diverged from the plain tokens path. The quieter thread points outward: as.matrix() returning a document-by-position integer matrix and as.tensor() handing off to torch::torch_tensor() make the tokenised corpus directly consumable by neural models rather than only by quanteda's own bag-of-words machinery.

◆ Prediction

The tensor and matrix export path is the least mature part of the surface and gained arguments in this release rather than settling, so expect further work there before the token internals change again.

Alternatives to fastglm and quanteda

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 fastglm or quanteda.

See all fastglm alternatives → · See all quanteda alternatives →

Recent activity from fastglm and quanteda

Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.

  1. 12d agoquantedaExplicit token recompilation and a denser path out to torch
  2. 2mo agofastglmFirth generalised to all families, plus SQUAREM and stability fixes
  3. 3mo agofastglmCRAN release 0.1.0
  4. 1y agoquantedaCorpus chunking and cheaper token concatenation
  5. 1y agoquantedaFaster concatenation and a dfm_lookup naming fix
  6. 2y agoquantedaMinor test and documentation fixes
  7. 2y agoquantedaPlatform-specific test and installation fixes
  8. 2y agoquantedaCRAN v4.0
  9. 4y agofastglmC++ headers exposed for linking
  10. 7y agofastglmFirst CRAN release of the C++ IRLS solver

Frequently asked questions

What is the difference between fastglm and quanteda?

Both compete on the same themes — r-package — within Analytics. quanteda is currently shipping more aggressively (velocity 2.5 vs 0.0), with 0 editorial sparks in the last 30 days against 0. See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.

Is fastglm better than quanteda?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. quanteda is currently shipping more aggressively (velocity 2.5 vs 0.0), with 0 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other Analytics products to evaluate alongside.

What are the best alternatives to fastglm?

Top fastglm alternatives in Analytics are ranked by recent ship velocity. Browse the "fastglm alternatives" section above for the current picks, or visit /alternatives/fastglm for the full list with editorial commentary on each.

What are the best alternatives to quanteda?

Top quanteda alternatives in Analytics are ranked by recent ship velocity. Browse the "quanteda alternatives" section above for the current picks, or visit /alternatives/quanteda for the full list with editorial commentary on each.