mrbayes
mrbayes spent 2026 auditing its own Bayesian MR estimators for coding errors.
A side-by-side editorial comparison of ggsci and tidypolars — release velocity, themes, recent moves, and the top alternatives to consider.
ggsci quietly became a palette mirror, then taught itself to generate colors on demand
ggsci ships ready-made ggplot2 color scales, originally journal and sci-fi palettes and now overwhelmingly terminal themes — the iTerm collection has grown past 400 entries and picks up 30 to 70 more with each sync. The one structural change in the recent run is gephi_palettes(), which generates distinct categorical colors for an arbitrary number of levels rather than serving a fixed list. Release cadence is steady, roughly every six to eight weeks.
tidypolars is grinding toward complete dplyr coverage, one supported function at a time
tidypolars lets you write dplyr and tidyr syntax against Polars DataFrames and LazyFrames. Its releases follow a fixed shape: raise the required polars version, add a handful of newly supported R functions and arguments, fix places where behaviour diverges from dplyr. Recent additions run from %notin% and as.integer() to .before/.after in mutate() and time zone handling in datetime parsing. Cadence is roughly every six to ten weeks and has not varied.
ggsci ships ready-made ggplot2 color scales, originally journal and sci-fi palettes and now overwhelmingly terminal themes — the iTerm collection has grown past 400 entries and picks up 30 to 70 more with each sync. The one structural change in the recent run is gephi_palettes(), which generates distinct categorical colors for an arbitrary number of levels rather than serving a fixed list. Release cadence is steady, roughly every six to eight weeks.
Two threads run in parallel. The larger one is curation: ggsci has effectively become a distribution channel for upstream color work, adding design-system palettes (Primer, Atlassian, Bootstrap, Tailwind) and re-syncing iTerm as that project changes, including correcting existing color values when upstream moves. The smaller and more interesting one is generation — the Gephi engine sidesteps the ceiling every fixed palette has, which is what happens when a plot needs more categories than any curated set provides.
Given how much of the release notes each cycle is a mechanical upstream sync, the plausible next step is automating those syncs rather than adding another vendor palette by hand; the Gephi generator is the more likely place any genuinely new capability appears.
tidypolars lets you write dplyr and tidyr syntax against Polars DataFrames and LazyFrames. Its releases follow a fixed shape: raise the required polars version, add a handful of newly supported R functions and arguments, fix places where behaviour diverges from dplyr. Recent additions run from %notin% and as.integer() to .before/.after in mutate() and time zone handling in datetime parsing. Cadence is roughly every six to ten weeks and has not varied.
Coverage is the whole strategy, and the target has been widening from dplyr into tidyr — unnest_longer_polars(), separate_longer_delim_polars() and separate_longer_position_polars() bring list-column and string-splitting verbs that have no Polars-idiomatic equivalent in the tidyverse dialect. The other consistent thread is fidelity: distinct() dropping unselected columns, summarize() dropping the last group, relocate() honouring tidy-select helpers, NULL in mutate() behaving as dplyr does. Each of these is a small breaking change made to match the reference rather than to differ from it.
The pattern of tracking the polars floor upward every release and following tidyverse changes closely — .by in fill() arrived when tidyr 1.3.2 shipped it — suggests the next releases continue mirroring new dplyr and tidyr arguments rather than adding a distinct capability.
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 ggsci or tidypolars.
mrbayes spent 2026 auditing its own Bayesian MR estimators for coding errors.
lineup2 ships once every few years, and 2026's release is a logo and a core-count tweak.
stringi has spent two years on build hardening since its Unicode 15.1 reset.
A 2017 chemometrics method frozen in place, visited only when CRAN changes its documentation rules.
A fast dplyr stand-in that keeps finding new places to skip work entirely.
Belgium's invasive-species indicator toolkit is in steady refinement, one plotting edge case at a time.
See all ggsci alternatives → · See all tidypolars alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — r — within Analytics. ggsci 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.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. ggsci 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.
Top ggsci alternatives in Analytics are ranked by recent ship velocity. Browse the "ggsci alternatives" section above for the current picks, or visit /alternatives/ggsci for the full list with editorial commentary on each.
Top tidypolars alternatives in Analytics are ranked by recent ship velocity. Browse the "tidypolars alternatives" section above for the current picks, or visit /alternatives/tidypolars for the full list with editorial commentary on each.