nflreadr
The nflverse data loader, whose releases are dictated by the NFL calendar and CRAN's archive policy
Comparison · Analytics
fastglm vs lstar
A side-by-side editorial comparison of fastglm and lstar — release velocity, themes, recent moves, and the top alternatives to consider.
fastglm vs lstar: 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 lstar?
A single-cell data store commits to Zarr v3 and range-readable hosting across four language surfaces
lstar stores single-cell data behind one C++ core with Python, R and JS/WASM bindings, and ships a browser viewer that reads the store directly. Zarr v3 is now the default on-disk format across all four surfaces, with zstd compression and sharding that packs many chunks into fewer objects. Viewer stores are compressed per field and resolved at chunk granularity, so a hosted viewer fetches only what it displays. The tag stream carries both lstar and lstar-sc releases.
fastglm vs lstar: 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.
lstar
5.0ANALYTICS
A single-cell data store commits to Zarr v3 and range-readable hosting across four language surfaces
◆ Current state
lstar stores single-cell data behind one C++ core with Python, R and JS/WASM bindings, and ships a browser viewer that reads the store directly. Zarr v3 is now the default on-disk format across all four surfaces, with zstd compression and sharding that packs many chunks into fewer objects. Viewer stores are compressed per field and resolved at chunk granularity, so a hosted viewer fetches only what it displays. The tag stream carries both lstar and lstar-sc releases.
◆ Where it's heading
The through-line is making a hosted store cheap to read. Sharding addresses the file-per-chunk explosion that makes many-chunk arrays awkward to host; per-field compression with chunk-granular resolution means colouring an embedding by one gene fetches one column rather than an array. The 0.2.x patches are the cost of maintaining four surfaces at once — a WASM heap crash that only browsers exercise, and a count-basis orientation defect where all three surfaces normalized in memory and none owned the on-disk layout.
◆ Prediction
The orientation bug's root cause — no surface owning the on-disk representation while all three normalized in memory — is the kind of gap that usually produces a validation or ownership change rather than another point fix.
Alternatives to fastglm and lstar
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 lstar.
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 lstar alternatives →
Recent activity from fastglm and lstar
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 21d agolstarViewer count-basis orientation fixed; existing stores need re-prep
- 26d agolstarWASM viewer crash on resizable heaps fixed
- 1mo agolstarlstar 0.2.0 ⚡
- 1mo agolstarMeasure state inferred from content, not slot name
- 2mo agofastglmFirth generalised to all families, plus SQUAREM and stability fixes
- 3mo agofastglmCRAN release 0.1.0 ⚡
- 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 lstar?
They serve adjacent needs but don't currently overlap on shipped themes. lstar is currently shipping more aggressively (velocity 5.0 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 lstar?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. lstar is currently shipping more aggressively (velocity 5.0 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 lstar?
Top lstar alternatives in Analytics are ranked by recent ship velocity. Browse the "lstar alternatives" section above for the current picks, or visit /alternatives/lstar for the full list with editorial commentary on each.