nanoparquet
nanoparquet is chasing byte-level agreement with the Java and Rust Parquet readers, not feature count.
Comparison · Analytics
lobstr vs mapsf
A side-by-side editorial comparison of lobstr and mapsf — release velocity, themes, recent moves, and the top alternatives to consider.
Shared themes:r-package
lobstr vs mapsf: at a glance
What is lobstr?
R's object inspector is losing its view of the internals as CRAN closes off the private C API.
lobstr exposes R's internal object representation — sizes, addresses, reference counts, abstract syntax trees. Its two most recent releases are both driven by R's move to a restricted public C API: 1.1.3 stopped reporting a vector's truelength and reworked the reference indicator into refs:n, and 1.2.0 changed what sxp(expand = "environment") shows in order to stay compliant. 1.2.0 also adds src() for exploring srcref objects.
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.
lobstr vs mapsf: editorial side-by-side
lobstr
0.0ANALYTICS
R's object inspector is losing its view of the internals as CRAN closes off the private C API.
◆ Current state
lobstr exposes R's internal object representation — sizes, addresses, reference counts, abstract syntax trees. Its two most recent releases are both driven by R's move to a restricted public C API: 1.1.3 stopped reporting a vector's truelength and reworked the reference indicator into refs:n, and 1.2.0 changed what sxp(expand = "environment") shows in order to stay compliant. 1.2.0 also adds src() for exploring srcref objects.
◆ Where it's heading
The package is being rebuilt inside a shrinking window of what R permits. Each release trades some introspection depth for API conformance while trying to keep the diagnostic value intact — showing promise expressions instead of internal frame structures, replacing named with a documented refs scale. Where the constraint does not bite, development continues normally: src() is genuinely new, and the environment-binding fixes remove long-standing errors on for-loop and immediate bindings.
◆ Prediction
Expect further conformance work, since the notes describe it as ongoing, with any remaining non-API-dependent readouts either reworked or dropped as R tightens further.
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.
Alternatives to lobstr and mapsf
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 lobstr or mapsf.
poissonreg
poissonreg gave its models away to parsnip and kept the glue — now it just keeps glmnet honest.
S7
S7 has stopped adding surface and started proving it holds up against R itself.
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.
See all lobstr alternatives → · See all mapsf alternatives →
Recent activity from lobstr and mapsf
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 agolobstrNew src() for srcrefs; environment bindings stop erroring
- 7mo agomapsfPNG resolution control and legend number formatting
- 9mo agolobstrtruelength reporting dropped for public C API compliance ⚡
- 1y agomapsf1.0.0 introduces theming and deprecates eight style arguments ⚡
- 1y agomapsfPencil-sketch layers, ckmeans breaks, and border extraction
- 2y agomapsfGraticule label display fix
- 4y agolobstrMoves to cpp11, relicensed MIT, adds experimental tree()
- 7y agolobstrPROTECT error fixed
- 7y agolobstrALTREP sizes computed correctly; obj_addr() stops side-effecting
Frequently asked questions
What is the difference between lobstr and mapsf?
Both compete on the same themes — r-package — within Analytics. lobstr and mapsf 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 lobstr better than mapsf?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. lobstr and mapsf 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 lobstr?
Top lobstr alternatives in Analytics are ranked by recent ship velocity. Browse the "lobstr alternatives" section above for the current picks, or visit /alternatives/lobstr for the full list with editorial commentary on each.
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.