S7
S7 has stopped adding surface and started proving it holds up against R itself.
Comparison · Analytics
mapsf vs textshaping
A side-by-side editorial comparison of mapsf and textshaping — release velocity, themes, recent moves, and the top alternatives to consider.
Shared themes:r-package
mapsf vs textshaping: at a glance
What is mapsf?
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.
What is textshaping?
Rewrote its shaping engine for bidirectional text, then spent a year fixing what that broke.
textshaping is the text layout layer beneath R's modern graphics stack, feeding ragg, ggplot2 and marquee. Version 1.0.0 rewrote the shaping engine to honour the global direction of text, adding a direction argument that defaults to automatic detection, align settings that resolve against that direction, and ICU-based soft break locations that handle ideographic scripts properly. The five releases since have been consecutive bug fixes against that rewrite — bidi embedding arrangement, line positioning with mixed sizes, a weak hash in the shape cache, a signed integer overflow, and font fallback regressions.
mapsf vs textshaping: editorial side-by-side
mapsf
0.0ANALYTICS
Thematic mapping in base R that finally got a theming system, then spent two years polishing legends.
◆ Current state
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.
◆ Where it's heading
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.
◆ Prediction
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.
textshaping
0.0ANALYTICS
Rewrote its shaping engine for bidirectional text, then spent a year fixing what that broke.
◆ Current state
textshaping is the text layout layer beneath R's modern graphics stack, feeding ragg, ggplot2 and marquee. Version 1.0.0 rewrote the shaping engine to honour the global direction of text, adding a direction argument that defaults to automatic detection, align settings that resolve against that direction, and ICU-based soft break locations that handle ideographic scripts properly. The five releases since have been consecutive bug fixes against that rewrite — bidi embedding arrangement, line positioning with mixed sizes, a weak hash in the shape cache, a signed integer overflow, and font fallback regressions.
◆ Where it's heading
The package has moved from Latin-first layout to script-agnostic layout in two rewrites, 0.4.0 and 1.0.0, and is now in the long correctness tail that follows. The bug reports arriving from ggplot2, ragg and marquee issue numbers show how it works in practice: textshaping bugs surface as rendering defects in the packages above it, which is why so many fixes here cite another package's issue tracker.
◆ Prediction
Expect continued fixes driven by downstream rendering reports rather than new layout features, as the 1.0.x series stabilises. The font fallback path has produced two of the recent bugs and is the most likely source of the next.
Alternatives to mapsf and textshaping
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 textshaping.
torchvision
R's torchvision is porting PyTorch's vision stack one task at a time — instance segmentation just landed.
datefixR
The messy-date parser rewrote its core in Rust and came out 300x faster.
maplegend
The legend engine mapsf spun out, now covering legend types the parent map package can draw.
lang
R help pages translated on demand by whichever LLM you point it at.
qualtRics
qualtRics moved its contact functions onto XM Directory days before the old endpoints died.
See all mapsf alternatives → · See all textshaping alternatives →
Recent activity from mapsf and textshaping
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 1mo agomapsfLabel placement arguments and deterministic distribution plots
- 2mo agomapsfBackground and extent control across the drawing functions
- 5mo agotextshapingFixes reverting between font fallbacks
- 7mo agomapsfPNG resolution control and legend number formatting
- 9mo agotextshapingGuards against freetype version mismatches with systemfonts
- 11mo agotextshapingFixes a signed integer overflow in the previous fix
- 11mo agotextshapingFixes bidi single-line shaping and a weak shape-cache hash
- 1y agomapsf1.0.0 introduces theming and deprecates eight style arguments ⚡
- 1y agotextshapingFixes hard line breaks across multiple embeddings
- 1y agotextshapingShaping engine rewritten to honour global text direction ⚡
- 1y agomapsfPencil-sketch layers, ckmeans breaks, and border extraction
- 2y agomapsfGraticule label display fix
Frequently asked questions
What is the difference between mapsf and textshaping?
Both compete on the same themes — r-package — within Analytics. mapsf and textshaping are shipping at a similar cadence (velocity 0.0 vs 0.0, both within Sparkpulse's "active" band). See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.
Is mapsf better than textshaping?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. mapsf and textshaping are shipping at a similar cadence (velocity 0.0 vs 0.0, both within Sparkpulse's "active" band). For your specific use case, the alternatives sections above list other Analytics products to evaluate alongside.
What are the best alternatives to mapsf?
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.
What are the best alternatives to textshaping?
Top textshaping alternatives in Analytics are ranked by recent ship velocity. Browse the "textshaping alternatives" section above for the current picks, or visit /alternatives/textshaping for the full list with editorial commentary on each.