fillpattern
Pattern fills for ggplot2, hardened against the ways users write sizes
A side-by-side editorial comparison of brglm2 and glmbayes — release velocity, themes, recent moves, and the top alternatives to consider.
A bias-reduction package reaches 1.0 by adding an estimator built for high-dimensional logistic regression
brglm2 fits generalized linear models using mean and median bias reduction rather than plain maximum likelihood, which matters most when ML estimates are infinite or badly biased. The 0.7-0.9 line broadened coverage — negative binomial via brnb(), ordinal superiority measures, the expo() method for exponentiated parameters, add1()/drop1() so step() stops silently producing nonsense. Version 1.0.0 in August 2025 added mdyplFit(), estimating logistic regression by maximum Diaconis-Ylvisaker prior penalized likelihood with optional high-dimensional corrections. The two releases since have tuned that new path.
A GPU-accelerated Bayesian GLM package buys its way into the standard R Bayesian toolchain
glmbayes fits Bayesian generalized linear models with optional OpenCL acceleration. The last four months moved it from a package with its own vocabulary to one that answers the insight and bayestestR generics the rest of the R Bayesian ecosystem is built on, while pushing the OpenCL kernels out into a separate nmathopencl dependency that carries CRAN Windows binaries. It returned to CRAN in August after an archival over a configure policy issue.
brglm2 fits generalized linear models using mean and median bias reduction rather than plain maximum likelihood, which matters most when ML estimates are infinite or badly biased. The 0.7-0.9 line broadened coverage — negative binomial via brnb(), ordinal superiority measures, the expo() method for exponentiated parameters, add1()/drop1() so step() stops silently producing nonsense. Version 1.0.0 in August 2025 added mdyplFit(), estimating logistic regression by maximum Diaconis-Ylvisaker prior penalized likelihood with optional high-dimensional corrections. The two releases since have tuned that new path.
The package's older work assumed the classical regime where observations comfortably outnumber parameters. mdyplFit() and its hd_correction argument target the opposite case, and the follow-up releases are almost entirely about it — Pearson residuals on original responses, aliased parameter handling, the sloe() signal-strength estimator ignoring leverage-one observations. Meanwhile the older surface gets graceful-failure work: brglm_fit() now returns its latest estimates with warnings rather than aborting.
Given that 1.0.1 and 1.1.0 are both dominated by mdyplFit follow-ups while the classical path receives only robustness fixes, further work on high-dimensional corrections is the likeliest direction.
glmbayes fits Bayesian generalized linear models with optional OpenCL acceleration. The last four months moved it from a package with its own vocabulary to one that answers the insight and bayestestR generics the rest of the R Bayesian ecosystem is built on, while pushing the OpenCL kernels out into a separate nmathopencl dependency that carries CRAN Windows binaries. It returned to CRAN in August after an archival over a configure policy issue.
The arc is about removing reasons not to use it. GPU support was previously blocked on Windows because the OpenCL kernels were vendored; splitting them into a CRAN package with binaries fixed that. The ecosystem work does the same thing for tooling — a glmb fit now responds to get_parameters, get_priors, simulate_prior and check_prior, so it drops into workflows built around easystats rather than requiring its own. The CRAN archival and the configure fixes that followed show how much of the effort goes into distribution rather than modelling.
get_priors() returning the full prior specification rather than a marginal table is the kind of detail that invites further bayestestR integration, and the diagnostic surface is the least built-out part of what has shipped so far.
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 brglm2 or glmbayes.
Pattern fills for ggplot2, hardened against the ways users write sizes
gcube's recent releases are all packaging metadata, not simulation code
The R port of Quinlan's Cubist gets reproducibility fixes, not new modelling
ggstats keeps widening what a coefficient or Likert plot can be
ecodive rebuilt itself into a broad diversity-metric library, breaking as it went
State-space data simulation for R, filled in one function at a time
See all brglm2 alternatives → · See all glmbayes alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — r-package — within Analytics. glmbayes is currently shipping more aggressively (velocity 6.3 vs 0.0), with 1 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.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. glmbayes is currently shipping more aggressively (velocity 6.3 vs 0.0), with 1 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.
Top brglm2 alternatives in Analytics are ranked by recent ship velocity. Browse the "brglm2 alternatives" section above for the current picks, or visit /alternatives/brglm2 for the full list with editorial commentary on each.
Top glmbayes alternatives in Analytics are ranked by recent ship velocity. Browse the "glmbayes alternatives" section above for the current picks, or visit /alternatives/glmbayes for the full list with editorial commentary on each.