rjdqa
rjdqa keeps refining one screen: the seasonal adjustment quality dashboard
A side-by-side editorial comparison of ggsci and tidytransit — 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.
tidytransit tracks the GTFS spec as it grows, one reader and one router feature at a time.
tidytransit reads GTFS transit feeds into tidy data frames and computes travel times using a RAPTOR implementation. Recent work splits between the reader keeping pace with the spec — locations.geojson in 1.7.0, empty strings parsed as NA in 1.8.0 — and the router gaining realism, most recently in-seat transfers. Feed specifications are now pulled from the automatically parsed GTFS reference rather than maintained by hand.
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.
tidytransit reads GTFS transit feeds into tidy data frames and computes travel times using a RAPTOR implementation. Recent work splits between the reader keeping pace with the spec — locations.geojson in 1.7.0, empty strings parsed as NA in 1.8.0 — and the router gaining realism, most recently in-seat transfers. Feed specifications are now pulled from the automatically parsed GTFS reference rather than maintained by hand.
The package has settled into tracking an external standard, which is why the changelog reads as a sequence of spec conformance items rather than a roadmap. Parsing responsibility keeps shifting outward to gtfsio, and data sources have moved with the ecosystem, from the retired transitfeeds API to MobilityData. Router changes are rarer than reader changes but land in the same releases.
Further GTFS spec features are the safest expectation, with GTFS-Flex the likeliest area now that locations.geojson reading is in place.
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 tidytransit.
rjdqa keeps refining one screen: the seasonal adjustment quality dashboard
epikit narrows to field-epidemiology helpers, handing proportions to a sibling package
SimInf 10.0 turns an epidemic simulator into a tool that fits models to real time series
A young package porting Stata's egen row-wise helpers to the tidyverse, one function per release
A statistician's personal toolbox, growing one plotting utility at a time
R/qtl is in pure custodial mode: every recent release answers a compiler, not a user
See all ggsci alternatives → · See all tidytransit 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 tidytransit alternatives in Analytics are ranked by recent ship velocity. Browse the "tidytransit alternatives" section above for the current picks, or visit /alternatives/tidytransit-r for the full list with editorial commentary on each.