Whatagraph
Whatagraph keeps fixing what breaks when one account runs a thousand sources.
A side-by-side editorial comparison of mapsf and RStudio — release velocity, themes, recent moves, and the top alternatives to consider.
Thematic mapping in base R that finally got a theming system, then spent two years polishing legends.
mapsf produces thematic maps on R's base graphics device — choropleths, proportional symbols, typology maps, rasters, and their combinations, with legends, scale bars, north arrows, and insets as composable elements. Version 1.0.0 was the structural release, introducing a theming system that deprecated eight scattered styling arguments and adding mf_png() and mf_svg() export helpers plus alpha transparency across map types. The 1.1.x and 1.2.x line since then has been steady refinement: background and extent control on the drawing functions, decimal and thousands-separator control in legends, and label placement arguments.
RStudio ships through release branches, and the notes are commit messages
RStudio's feed is a run of release-branch tags — Yellow Yarrow, Pacific Dogwood, Golden Wattle — each carrying a backported fix rather than an announced feature. The newest tag restores a Windows install rule that had been deleted alongside an unrelated winpty block, leaving the shipped installer without a 32-bit rsession binary and breaking 32-bit R entirely. What reaches users is legible only if you read the commit body.
mapsf produces thematic maps on R's base graphics device — choropleths, proportional symbols, typology maps, rasters, and their combinations, with legends, scale bars, north arrows, and insets as composable elements. Version 1.0.0 was the structural release, introducing a theming system that deprecated eight scattered styling arguments and adding mf_png() and mf_svg() export helpers plus alpha transparency across map types. The 1.1.x and 1.2.x line since then has been steady refinement: background and extent control on the drawing functions, decimal and thousands-separator control in legends, and label placement arguments.
The package has been consolidating control into fewer, more consistent places. Legend handling moved out to the maplegend package in 0.8.0 and the per-element mf_legend_* functions were deprecated in favor of arguments on the map calls themselves; theming replaced ad-hoc style arguments in 1.0.0; and recent releases keep propagating the same argument vocabulary — bg, extent, leg_val_rnd, leg_val_dec, leg_val_big — across every function that should accept it. Determinism is a visible concern too, with 1.2.1 fixing a seed so mf_distr() point positions stop moving between runs.
The recent releases are almost entirely argument-parity work across existing functions, so expect that to continue until the vocabulary is uniform rather than any new map type appearing.
RStudio's feed is a run of release-branch tags — Yellow Yarrow, Pacific Dogwood, Golden Wattle — each carrying a backported fix rather than an announced feature. The newest tag restores a Windows install rule that had been deleted alongside an unrelated winpty block, leaving the shipped installer without a 32-bit rsession binary and breaking 32-bit R entirely. What reaches users is legible only if you read the commit body.
Two areas absorb nearly all the visible work: Windows packaging correctness and Posit Assistant plumbing — SHA-256 verification of assistant downloads, gating .positai/.claude ignore-file edits on the directories actually existing. Both read as cleanup after features landed elsewhere. The release-branch structure means the same fix often appears twice, once on main and once backported, so tag count overstates the pace of change.
Expect further Yellow Yarrow tags in the same shape — a single backported fix per tag, its description written for reviewers rather than users. Posit Assistant integration is the most likely source of the next visible change, since it is the only area here still gaining behavior rather than losing bugs.
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 mapsf or RStudio.
Whatagraph keeps fixing what breaks when one account runs a thousand sources.
Lightdash keeps handing authoring to outside agents and keeping the governed layer for itself.
A 4.4.0 tag appears, but the feed carries only its release plumbing
distributions3 0.3.0 adds sample-based distributions and likelihood derivatives
Basedash keeps pushing its data out of the workspace — now to people without accounts
dbt Fusion's second beta is adapter work: ClickHouse gets materializations, indexes, and catalogs
See all mapsf alternatives → · See all RStudio alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. RStudio 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.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. RStudio 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.
Top mapsf alternatives in Analytics are ranked by recent ship velocity. Browse the "mapsf alternatives" section above for the current picks, or visit /alternatives/mapsf for the full list with editorial commentary on each.
Top RStudio alternatives in Analytics are ranked by recent ship velocity. Browse the "RStudio alternatives" section above for the current picks, or visit /alternatives/rstudio for the full list with editorial commentary on each.