osmapiR
osmapiR is the rare API client that tracks its server's wiki revision numbers in the changelog.
Comparison · Analytics
lobstr vs nanoparquet
A side-by-side editorial comparison of lobstr and nanoparquet — release velocity, themes, recent moves, and the top alternatives to consider.
lobstr vs nanoparquet: 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 nanoparquet?
nanoparquet is chasing byte-level agreement with the Java and Rust Parquet readers, not feature count.
nanoparquet reads and writes Parquet from R with no Arrow dependency, which is its entire reason to exist. The 0.4.0 line renamed the reader API and added schema authoring plus `append_parquet()`, and the 0.5.x releases have gone after interoperability: definition and repetition level encodings the Apache Parquet Java library expects, flatbuffer alignment the Rust arrow-rs reader expects, 128-bit decimals, and Polars-written files that omit the dictionary page offset. The newest release adds `bit64::integer64` columns and writing to stdout.
lobstr vs nanoparquet: 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.
nanoparquet
0.0ANALYTICS
nanoparquet is chasing byte-level agreement with the Java and Rust Parquet readers, not feature count.
◆ Current state
nanoparquet reads and writes Parquet from R with no Arrow dependency, which is its entire reason to exist. The 0.4.0 line renamed the reader API and added schema authoring plus `append_parquet()`, and the 0.5.x releases have gone after interoperability: definition and repetition level encodings the Apache Parquet Java library expects, flatbuffer alignment the Rust arrow-rs reader expects, 128-bit decimals, and Polars-written files that omit the dictionary page offset. The newest release adds `bit64::integer64` columns and writing to stdout.
◆ Where it's heading
Almost every entry since 0.4.0 names another engine — Java, arrow-rs, Polars, Arrow schema metadata — which tells you the maintainers are treating cross-reader fidelity as the product rather than R-side ergonomics. The type system is filling in from the edges: DECIMAL beyond 8 bytes, UUID, FLOAT16 and INTERVAL as raw lists, and now 64-bit integers with an explicit read-type option instead of a silent cast to double. Writing to `:stdout:` points at a second audience, shell pipelines rather than interactive R.
◆ Prediction
The remaining unmapped Parquet types the changelog has been parking in raw-vector lists — FLOAT16 and INTERVAL — are the obvious next targets, following the same pattern by which DECIMAL and UUID graduated to real R types.
Alternatives to lobstr and nanoparquet
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 nanoparquet.
ymlthis
ymlthis retired itself, naming Quarto as the reason it no longer needs to exist.
forestly
forestly built an interactive safety review tool, then taught it to produce submission-ready RTF.
pharmaverseadam
pharmaverseadam is the pharmaverse's test-data mirror, and it now covers neurology.
pkglite
pkglite's whole job is knowing which files in an R package are text — and it keeps getting better at guessing.
gMCPLite
gMCPLite exists to be gMCP without Java, and its releases guard that boundary rather than extend it.
See all lobstr alternatives → · See all nanoparquet alternatives →
Recent activity from lobstr and nanoparquet
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 3mo agonanoparquet64-bit integer columns and writing Parquet to stdout
- 4mo agonanoparquetFiles now readable by the Java and Rust Parquet libraries
- 5mo agolobstrNew src() for srcrefs; environment bindings stop erroring
- 9mo agolobstrtruelength reporting dropped for public C API compliance ⚡
- 1y agonanoparquetReads Polars files that omit the dictionary page offset
- 1y agonanoparquetDate, FLOAT, and mixed-encoding read fixes
- 1y agonanoparquetSchema authoring and append_parquet arrive with a renamed API ⚡
- 1y agonanoparquetFixes a write_parquet crash
- 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 nanoparquet?
They serve adjacent needs but don't currently overlap on shipped themes. lobstr and nanoparquet 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 nanoparquet?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. lobstr and nanoparquet 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 nanoparquet?
Top nanoparquet alternatives in Analytics are ranked by recent ship velocity. Browse the "nanoparquet alternatives" section above for the current picks, or visit /alternatives/nanoparquet for the full list with editorial commentary on each.