PurpleAir
The R client for PurpleAir sensors keeps finding its time-averaging was wrong.
Comparison · Analytics
quanteda vs treasury
A side-by-side editorial comparison of quanteda and treasury — release velocity, themes, recent moves, and the top alternatives to consider.
Shared themes:r-package
quanteda vs treasury: at a glance
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.
What is treasury?
A thin Treasury rates wrapper has stopped adding endpoints and started making its tables self-describing.
treasury wraps the US Treasury's published rate feeds — bill rates, par yields, forward rates, long-term extrapolated rates, and the HQM and breakeven inflation curves — into one set of R functions. Since 0.3.0 every function returns a data.table, and 0.5.0 added optional on-disk response caching with a one-day default. The most recent release is about data fidelity rather than reach: identifying columns, correct maturity labels, and locale-safe date parsing.
quanteda vs treasury: editorial side-by-side
quanteda
2.5ANALYTICS
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.
treasury
0.0ANALYTICS
A thin Treasury rates wrapper has stopped adding endpoints and started making its tables self-describing.
◆ Current state
treasury wraps the US Treasury's published rate feeds — bill rates, par yields, forward rates, long-term extrapolated rates, and the HQM and breakeven inflation curves — into one set of R functions. Since 0.3.0 every function returns a data.table, and 0.5.0 added optional on-disk response caching with a one-day default. The most recent release is about data fidelity rather than reach: identifying columns, correct maturity labels, and locale-safe date parsing.
◆ Where it's heading
Endpoint coverage looks essentially complete, so the work has moved to the metadata a downstream analyst needs to join and audit results — cusip and maturity_date on bill quotes, the feed's updated_at stamp, and the extrapolation factor behind 2002-2006 long-term rate estimates. Error handling is tightening in the same direction: an out-of-range month now fails with a message instead of quietly returning nothing. That is the profile of a wrapper moving from coverage to correctness, where the remaining bugs are the subtle ones that only surface in other people's locales.
◆ Prediction
Expect further column-level enrichment and input validation on the endpoints already covered rather than new data sources, since the structural pieces — data.table returns and caching — are already in place.
Alternatives to quanteda and treasury
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 or treasury.
piecepackr
A board game graphics package runs one of the most disciplined deprecation cycles in R.
e2tree
The explainable-ensemble-tree package now measures whether its own explanations are faithful.
discretefdr
The discrete-data FDR package is being pared into one piece of a larger multiple-testing suite.
contentanalysis
A scientific-text analysis package moved from counting citations to classifying argument structure.
relialearnr
The teaching arm of an R reliability suite keeps pace with whatever its analysis siblings ship.
See all quanteda alternatives → · See all treasury alternatives →
Recent activity from quanteda and treasury
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 12d agoquantedaExplicit token recompilation and a denser path out to torch
- 1mo agotreasuryBill rates gain CUSIP and maturity date; locale bug fixed
- 4mo agotreasuryOptional response caching, one day by default
- 11mo agotreasuryRate functions renamed to singular for consistency
- 1y agotreasuryEvery function now returns a data.table ⚡
- 1y agoquantedaCorpus chunking and cheaper token concatenation
- 1y agoquantedaFaster concatenation and a dfm_lookup naming fix
- 2y agotreasuryHQM, coupon-issue and breakeven inflation curves added
- 2y agoquantedaMinor test and documentation fixes
- 2y agoquantedaPlatform-specific test and installation fixes
- 2y agoquantedaCRAN v4.0 ⚡
Frequently asked questions
What is the difference between quanteda and treasury?
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 quanteda better than treasury?
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 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.
What are the best alternatives to treasury?
Top treasury alternatives in Analytics are ranked by recent ship velocity. Browse the "treasury alternatives" section above for the current picks, or visit /alternatives/treasury for the full list with editorial commentary on each.