r2rtf
The clinical-report table engine learned Chinese, then learned to leave RTF entirely
Comparison · Analytics
crul vs nanoparquet
A side-by-side editorial comparison of crul and nanoparquet — release velocity, themes, recent moves, and the top alternatives to consider.
crul vs nanoparquet: at a glance
What is crul?
crul took mocking back from webmockr and made it a property of the client itself
crul is the R6-based HTTP client underneath much of rOpenSci's package stack, covering synchronous requests, three flavours of async, pagination and retries. Its 1.6.0 release in July 2025 changed where test mocking lives: each client — HttpClient, Async, AsyncVaried — now takes a mocking parameter at initialisation or per method, and the standalone mock() function is deprecated. Mocking used to be something webmockr switched on from outside; it is now a setting on the client.
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.
crul vs nanoparquet: editorial side-by-side
crul
0.0ANALYTICS
crul took mocking back from webmockr and made it a property of the client itself
◆ Current state
crul is the R6-based HTTP client underneath much of rOpenSci's package stack, covering synchronous requests, three flavours of async, pagination and retries. Its 1.6.0 release in July 2025 changed where test mocking lives: each client — HttpClient, Async, AsyncVaried — now takes a mocking parameter at initialisation or per method, and the standalone mock() function is deprecated. Mocking used to be something webmockr switched on from outside; it is now a setting on the client.
◆ Where it's heading
The async surface has been the growth area for years — retries reached Async, AsyncVaried, AsyncQueue and HttpRequest in 1.4, AsyncQueue gained the response accessors in 1.2, and 1.5.0 wired async requests up to webmockr. The 1.6.0 change reverses that direction of dependency, and it landed within a minute of webmockr's own release severing its tie to vcr. Read together, the rOpenSci HTTP stack is being deliberately untangled so each package can be used without the others.
◆ Prediction
With mock() deprecated rather than removed, the next major release is the likely point of deletion. Expect the remaining work to follow the same decoupling theme rather than adding request features.
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 crul 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 crul or nanoparquet.
DoseFinding
New stewardship at openpharma, then two releases adding the methods MCP-Mod was missing
webmockr
The stubbing library added httr2 support, then spent a year cutting itself free of everything else
dendroNetwork
Six releases, six identical bodies — the feed carries the package abstract instead of release notes
chattr
chattr deleted every LLM integration it had written and outsourced the lot to ellmer
cloudml
Six years since the last functional change, and Google renamed the service it wraps in the release before that
See all crul alternatives → · See all nanoparquet alternatives →
Recent activity from crul 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
- 1y agocrulMocking becomes a client parameter, independent of webmockr ⚡
- 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
- 2y agocrulAsync requests become mockable through webmockr
- 2y agocrulDocumentation fixes and test helper tweak
- 3y agocrulHTTP retries reach the async classes
- 3y agocrulClearer error for mismatched urls and disk lengths
- 4y agocrulAsyncQueue gains response accessors; results print as a summary
Frequently asked questions
What is the difference between crul and nanoparquet?
They serve adjacent needs but don't currently overlap on shipped themes. crul 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 crul better than nanoparquet?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. crul 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 crul?
Top crul alternatives in Analytics are ranked by recent ship velocity. Browse the "crul alternatives" section above for the current picks, or visit /alternatives/crul 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.