nflreadr
The nflverse data loader, whose releases are dictated by the NFL calendar and CRAN's archive policy
Comparison · Analytics
fastglm vs PurpleAir
A side-by-side editorial comparison of fastglm and PurpleAir — release velocity, themes, recent moves, and the top alternatives to consider.
Shared themes:r-package
fastglm vs PurpleAir: at a glance
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.
What is PurpleAir?
The R client for PurpleAir sensors keeps finding its time-averaging was wrong.
PurpleAir is a small R client for the PurpleAir air quality sensor API, covering sensor queries, historical readings, and — more recently — finding a sensor on the local network by IP address and id. Authentication has been simplified to an environment variable only, with the redundant key argument removed. The package is maintained reactively, and most of what ships is correctness work on the queries it already makes.
fastglm vs PurpleAir: editorial side-by-side
fastglm
0.0ANALYTICS
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.
PurpleAir
0.0ANALYTICS
The R client for PurpleAir sensors keeps finding its time-averaging was wrong.
◆ Current state
PurpleAir is a small R client for the PurpleAir air quality sensor API, covering sensor queries, historical readings, and — more recently — finding a sensor on the local network by IP address and id. Authentication has been simplified to an environment variable only, with the redundant key argument removed. The package is maintained reactively, and most of what ships is correctness work on the queries it already makes.
◆ Where it's heading
The recurring theme is time aggregation. Weekly, monthly and yearly average intervals were wrong and fixed in one release; the weekly average was wrong again and fixed in the next. For an air quality package that is not incidental — averaging window is what turns a stream of sensor readings into an exposure estimate, and downstream analyses inherit the error silently. The other thread is failing earlier and more clearly: explicit errors for spatial inputs the sensor query does not accept, better index parsing so malformed requests never reach the API, and handling for history calls that return nothing. Local sensor discovery is the one genuine capability addition, opening a path that does not depend on the cloud API at all.
◆ Prediction
On this record, further aggregation and input-validation fixes are the likeliest next releases; whether local network access grows past discovery into full local data retrieval is not something the entries indicate.
Alternatives to fastglm and PurpleAir
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 PurpleAir.
susier
Fine-mapping workhorse susieR spends its releases hunting null-effect trimming bugs
UCell
A rank-based gene signature scorer that has grown by adapting to whatever object format single-cell R uses next
detectseparation
A diagnostic package that generalized past its own name, then learned to say which kind of separation it found
brglm2
A bias-reduction package reaches 1.0 by adding an estimator built for high-dimensional logistic regression
bayestools
The JAGS toolkit under RoBMA, shipping the standardization machinery its downstream rewrite needed
See all fastglm alternatives → · See all PurpleAir alternatives →
Recent activity from fastglm and PurpleAir
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 2mo agofastglmFirth generalised to all families, plus SQUAREM and stability fixes
- 3mo agoPurpleAirWeekly averages fixed again; API key argument dropped
- 3mo agofastglmCRAN release 0.1.0 ⚡
- 10mo agoPurpleAirLocal sensor discovery, and averaging intervals corrected
- 1y agoPurpleAirBounding box sensor queries fixed
- 4y agofastglmC++ headers exposed for linking
- 7y agofastglmFirst CRAN release of the C++ IRLS solver
Frequently asked questions
What is the difference between fastglm and PurpleAir?
Both compete on the same themes — r-package — within Analytics. fastglm and PurpleAir 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.
Is fastglm better than PurpleAir?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. fastglm and PurpleAir 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.
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 PurpleAir?
Top PurpleAir alternatives in Analytics are ranked by recent ship velocity. Browse the "PurpleAir alternatives" section above for the current picks, or visit /alternatives/purpleair for the full list with editorial commentary on each.