gcube
gcube's recent releases are all packaging metadata, not simulation code
Comparison · Analytics
fillpattern vs quanteda
A side-by-side editorial comparison of fillpattern and quanteda — release velocity, themes, recent moves, and the top alternatives to consider.
Shared themes:r-package
fillpattern vs quanteda: at a glance
What is fillpattern?
Pattern fills for ggplot2, hardened against the ways users write sizes
fillpattern provides pattern fills — stripes, bricks, dots — for ggplot2 and base R graphics, aimed at figures that must stay legible in greyscale or to colour-blind readers. The 1.0.3 release is mostly defensive: size modifier strings ending in a colon no longer swap width for height, modify_size() reports invalid units instead of crashing and understands in, inches and cm, and a background colour bug in scale_fill_pattern() is fixed. The minimum R version rises to 4.2.0 for recent graphics engine features.
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.
fillpattern vs quanteda: editorial side-by-side
fillpattern
0.0ANALYTICS
Pattern fills for ggplot2, hardened against the ways users write sizes
◆ Current state
fillpattern provides pattern fills — stripes, bricks, dots — for ggplot2 and base R graphics, aimed at figures that must stay legible in greyscale or to colour-blind readers. The 1.0.3 release is mostly defensive: size modifier strings ending in a colon no longer swap width for height, modify_size() reports invalid units instead of crashing and understands in, inches and cm, and a background colour bug in scale_fill_pattern() is fixed. The minimum R version rises to 4.2.0 for recent graphics engine features.
◆ Where it's heading
Development is slow and entirely reactive to how the string-based size interface fails. The pattern across releases is the same: a user hits an edge — very small fill areas in 1.0.2, malformed unit strings in 1.0.3 — and the fix is either a graceful fallback or a clearer error. Leaning on R's newer graphics engine rather than reimplementing pattern rendering keeps the package small at the cost of raising its version floor.
◆ Prediction
Expect further releases to stay in the same register: parsing and validation fixes for the size and unit interface, with the pattern set itself unlikely to change.
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.
Alternatives to fillpattern 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 fillpattern or quanteda.
cubist
The R port of Quinlan's Cubist gets reproducibility fixes, not new modelling
ggstats
ggstats keeps widening what a coefficient or Likert plot can be
ecodive
ecodive rebuilt itself into a broad diversity-metric library, breaking as it went
simStateSpace
State-space data simulation for R, filled in one function at a time
rollama
rollama turns a local-LLM wrapper into an instrument for reproducible annotation
See all fillpattern alternatives → · See all quanteda alternatives →
Recent activity from fillpattern and quanteda
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 12d agoquantedaExplicit token recompilation and a denser path out to torch
- 6mo agofillpatternSize string parsing fixed; invalid units now report instead of crash
- 1y agoquantedaCorpus chunking and cheaper token concatenation
- 1y agoquantedaFaster concatenation and a dfm_lookup naming fix
- 2y agofillpatternSmall fill areas no longer crash; min_size falls back to solid
- 2y agoquantedaMinor test and documentation fixes
- 2y agoquantedaPlatform-specific test and installation fixes
- 2y agoquantedaCRAN v4.0 ⚡
- 2y agofillpatternfillpattern 1.0.1
Frequently asked questions
What is the difference between fillpattern 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 fillpattern 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 fillpattern?
Top fillpattern alternatives in Analytics are ranked by recent ship velocity. Browse the "fillpattern alternatives" section above for the current picks, or visit /alternatives/fillpattern 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.