r2rtf
The clinical-report table engine learned Chinese, then learned to leave RTF entirely
A side-by-side editorial comparison of mapsf and slider — 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.
Feature-complete since 2021, and every release since has been paying CRAN's C API bill
slider provides sliding-window and index-aware window functions for R, with a C implementation underneath and a specialised fast path for common aggregations. The user-facing surface has been stable since 0.3.0 in late 2022. Everything after that is compliance and platform work: STRING_PTR removed in 0.3.2, OBJECT() removed in 0.3.3, a vctrs callable's C signature corrected, and the minimum R version raised twice.
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.
slider provides sliding-window and index-aware window functions for R, with a C implementation underneath and a specialised fast path for common aggregations. The user-facing surface has been stable since 0.3.0 in late 2022. Everything after that is compliance and platform work: STRING_PTR removed in 0.3.2, OBJECT() removed in 0.3.3, a vctrs callable's C signature corrected, and the minimum R version raised twice.
Two forces set the release schedule, and neither is feature demand. The first is CRAN closing off non-API C entry points, which packages reaching into R internals for speed have to unwind one accessor at a time — slider is on its second such release with no visible loss of function. The second is vctrs, whose breaking changes slider absorbs ahead of time; 0.2.2 exists solely to prepare for one. The last release that added anything callers can see was 0.3.0's slider_plus() and slider_minus() extension hooks.
Expect the pattern to continue: another non-API accessor removal or a vctrs compatibility release, rather than new window functions. The C-level surface is the only part of this package still moving.
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 slider.
The clinical-report table engine learned Chinese, then learned to leave RTF entirely
New stewardship at openpharma, then two releases adding the methods MCP-Mod was missing
The stubbing library added httr2 support, then spent a year cutting itself free of everything else
crul took mocking back from webmockr and made it a property of the client itself
Six releases, six identical bodies — the feed carries the package abstract instead of release notes
chattr deleted every LLM integration it had written and outsourced the lot to ellmer
See all mapsf alternatives → · See all slider alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. mapsf and slider 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.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. mapsf and slider 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.
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 slider alternatives in Analytics are ranked by recent ship velocity. Browse the "slider alternatives" section above for the current picks, or visit /alternatives/slider for the full list with editorial commentary on each.