osmapiR
osmapiR is the rare API client that tracks its server's wiki revision numbers in the changelog.
Comparison · Analytics
marquee vs nanoparquet
A side-by-side editorial comparison of marquee and nanoparquet — release velocity, themes, recent moves, and the top alternatives to consider.
marquee vs nanoparquet: at a glance
What is marquee?
marquee is filling in the typographic details — outlines, border types, real font metrics for underlines.
marquee renders markdown text onto R graphics devices, and backs element_marquee() and geom_marquee() in ggplot2. Development ran in a tight burst through August and September 2025: 1.1.0 added text outlines, a size shortcut and remote PNG/JPEG support, 1.2.0 added border and outline line types and moved underline placement onto font metrics, and 1.2.1 cleaned up the bugs those introduced.
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.
marquee vs nanoparquet: editorial side-by-side
marquee
0.0ANALYTICS
marquee is filling in the typographic details — outlines, border types, real font metrics for underlines.
◆ Current state
marquee renders markdown text onto R graphics devices, and backs element_marquee() and geom_marquee() in ggplot2. Development ran in a tight burst through August and September 2025: 1.1.0 added text outlines, a size shortcut and remote PNG/JPEG support, 1.2.0 added border and outline line types and moved underline placement onto font metrics, and 1.2.1 cleaned up the bugs those introduced.
◆ Where it's heading
The package is converging on typographic fidelity rather than new capability. Early work settled layout semantics — CSS margin collapsing, inline padding reserving space during shaping, devices without glyph support — and recent releases refine how decorations are drawn and measured. The naming cleanup in 1.2.0, border_size becoming border_width, reads as an API being tidied ahead of wider use rather than one still being explored.
◆ Prediction
Expect continued small releases sanding down rendering edge cases in ggplot2 contexts, since that is where the recent bug reports come from; nothing here signals a new feature area.
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 marquee 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 marquee 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 marquee alternatives → · See all nanoparquet alternatives →
Recent activity from marquee 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
- 11mo agomarqueeBug fixes for relative sizes, outlines and guide width
- 11mo agomarqueeBorder and outline line types; underlines follow font metrics
- 11mo agomarqueeRotated text width fixed; factor input supported
- 0y agomarqueeText outlines, size shortcuts and images from URLs
- 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 agomarquee1.0 settles margin collapsing and inline decoration spacing
- 1y agonanoparquetFixes a write_parquet crash
Frequently asked questions
What is the difference between marquee and nanoparquet?
They serve adjacent needs but don't currently overlap on shipped themes. marquee 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 marquee better than nanoparquet?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. marquee 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 marquee?
Top marquee alternatives in Analytics are ranked by recent ship velocity. Browse the "marquee alternatives" section above for the current picks, or visit /alternatives/marquee 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.