osmapiR
osmapiR is the rare API client that tracks its server's wiki revision numbers in the changelog.
Comparison · Analytics
Athlytics vs nanoparquet
A side-by-side editorial comparison of Athlytics and nanoparquet — release velocity, themes, recent moves, and the top alternatives to consider.
Athlytics vs nanoparquet: at a glance
What is Athlytics?
A Strava analytics package spent its 1.0 cycle surviving rOpenSci review, not adding features.
Athlytics computes endurance-training metrics — ACWR, EWMA load, efficiency factor, decoupling, personal bests — from Strava exports. Every release in view is review-driven: test-suite consolidation, dataset renames, styler passes, and a substantial robustness pass over the metric calculations and stream parsers. 1.0.6 explicitly changes nothing but packaging metadata.
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.
Athlytics vs nanoparquet: editorial side-by-side
Athlytics
0.0ANALYTICS
A Strava analytics package spent its 1.0 cycle surviving rOpenSci review, not adding features.
◆ Current state
Athlytics computes endurance-training metrics — ACWR, EWMA load, efficiency factor, decoupling, personal bests — from Strava exports. Every release in view is review-driven: test-suite consolidation, dataset renames, styler passes, and a substantial robustness pass over the metric calculations and stream parsers. 1.0.6 explicitly changes nothing but packaging metadata.
◆ Where it's heading
The package is optimising for credibility rather than surface area. It completed rOpenSci peer review, moved to an offline ZIP export workflow with hardened TCX/GPX parsing, corrected the EWMA half-life mapping, and deliberately softened its ACWR language away from injury-risk claims. Version numbers are also being published out of order, which makes the feed a poor guide to what shipped when.
◆ Prediction
With review complete and packaging metadata frozen for archival, the next substantive release is more likely to extend metric coverage or data sources than to continue polishing; nothing in these entries points to a specific new metric.
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 Athlytics 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 Athlytics 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 Athlytics alternatives → · See all nanoparquet alternatives →
Recent activity from Athlytics and nanoparquet
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 2mo agoAthlyticsPackaging metadata standardised for archival
- 2mo agoAthlyticsrOpenSci peer review completed; test suite consolidated
- 2mo agoAthlyticsACWR and stream parsing corrected for real-world exports
- 3mo agonanoparquet64-bit integer columns and writing Parquet to stdout
- 4mo agonanoparquetFiles now readable by the Java and Rust Parquet libraries
- 6mo agoAthlyticsv1.0.2: Documentation & Review Fixes
- 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
Frequently asked questions
What is the difference between Athlytics and nanoparquet?
They serve adjacent needs but don't currently overlap on shipped themes. Athlytics 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 Athlytics better than nanoparquet?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Athlytics 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 Athlytics?
Top Athlytics alternatives in Analytics are ranked by recent ship velocity. Browse the "Athlytics alternatives" section above for the current picks, or visit /alternatives/athlytics 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.