r2rtf
The clinical-report table engine learned Chinese, then learned to leave RTF entirely
A side-by-side editorial comparison of mapsf and pysparklyr — 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.
Posit's Spark Connect bridge keeps adding backends — and now runs tidymodels tuning on the cluster.
pysparklyr is the Python-backed backend that lets sparklyr talk to Spark Connect, Databricks Connect, and now Snowflake, handling the reticulate environment, authentication, and Arrow configuration so R users mostly do not have to. The 0.2.x line has widened it well past a connectivity shim: 0.2.0 brought the Spark 4.0 ML function family and Snowpark Connect, and 0.2.2 added tune_grid_spark() so a tidymodels tuning grid executes inside a Spark Connect cluster. Authentication has become a first-class concern, with Snowflake's native authenticators, connections.toml discovery, and Posit Connect viewer credentials all supported.
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.
pysparklyr is the Python-backed backend that lets sparklyr talk to Spark Connect, Databricks Connect, and now Snowflake, handling the reticulate environment, authentication, and Arrow configuration so R users mostly do not have to. The 0.2.x line has widened it well past a connectivity shim: 0.2.0 brought the Spark 4.0 ML function family and Snowpark Connect, and 0.2.2 added tune_grid_spark() so a tidymodels tuning grid executes inside a Spark Connect cluster. Authentication has become a first-class concern, with Snowflake's native authenticators, connections.toml discovery, and Posit Connect viewer credentials all supported.
Two directions are running at once. Horizontally, the package is becoming backend-plural — what started as Databricks-and-Spark now covers Snowflake through Snowpark Connect, with credential handling generalized per platform rather than special-cased. Vertically, it is climbing from data manipulation toward modeling: distributed ML functions in 0.2.0, distributed tuning in 0.2.2. A persistent third thread is absorbing upstream churn — Pandas 3.0 conversion, sparklyr 1.9.5 and dbplyr 2.6.0 restructuring the tbl source slot, reticulate's changing environment management.
With tuning distributed and the Spark 4.0 ML surface in place, the unfinished edge is the rest of the tidymodels workflow — expect fitting and resampling paths to follow tune_grid_spark() onto the cluster.
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 pysparklyr.
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 pysparklyr alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. pysparklyr is currently shipping more aggressively (velocity 3.8 vs 0.0), with 1 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. pysparklyr is currently shipping more aggressively (velocity 3.8 vs 0.0), with 1 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 pysparklyr alternatives in Analytics are ranked by recent ship velocity. Browse the "pysparklyr alternatives" section above for the current picks, or visit /alternatives/pysparklyr for the full list with editorial commentary on each.