mice
mice can finally predict, not just estimate, from multiply imputed data.
Comparison · Infra & APIs
valr vs writeAlizer
A side-by-side editorial comparison of valr and writeAlizer — release velocity, themes, recent moves, and the top alternatives to consider.
valr vs writeAlizer: at a glance
What is valr?
valr's interval verbs now read genomic files in place instead of demanding a loaded tibble.
valr reimplements bedtools-style genome interval arithmetic as tidyverse verbs backed by C++. Its long project has been closing the behavioural gap with bedtools — the book-ended interval semantics finally match in 0.10.0, three releases after the deprecation began. The July release also ends the assumption that intervals must be in memory: bed_map(), bed_intersect(), bed_subtract(), bed_coverage() and bed_window() accept a bigWig or bigBed path or URL where an interval table used to go.
What is writeAlizer?
Six months of releases and not one of them touched the scoring models
writeAlizer generates predicted writing-quality scores from features produced by Coh-Metrix, ReaderBench and GAMET, downloading its trained scoring models on demand. Every release in this window — nine of them between September 2025 and February 2026 — is about that download path rather than the scoring: classed error conditions, checksum verification, an offline mode, a mockable artifact directory, and dependency reporting for the model families a user actually invokes.
valr vs writeAlizer: editorial side-by-side
valr
0.0INFRA · APIS
valr's interval verbs now read genomic files in place instead of demanding a loaded tibble.
◆ Current state
valr reimplements bedtools-style genome interval arithmetic as tidyverse verbs backed by C++. Its long project has been closing the behavioural gap with bedtools — the book-ended interval semantics finally match in 0.10.0, three releases after the deprecation began. The July release also ends the assumption that intervals must be in memory: bed_map(), bed_intersect(), bed_subtract(), bed_coverage() and bed_window() accept a bigWig or bigBed path or URL where an interval table used to go.
◆ Where it's heading
Two arcs converge here. One is compatibility: min_overlap arrived with a deprecation warning in 0.9.0 and its default flipped from 0 to 1 in 0.10.0, so book-ended intervals are excluded by default as bedtools does, with the internal calculations in bed_closest() and friends deliberately left counting them. The other is the file-backed path, which grew out of the cpp11bigwig dependency adopted in 0.8.3 for read_bigwig() and re-exported in 0.9.0 — reading a file became querying one. Underneath, the C++ base keeps getting lighter: Rcpp swapped for cpp11, rlang cut to a single function, per-group memory copies removed from three verbs.
◆ Prediction
Only five verbs take a file argument today and bed_closest(), bed_glyph() and the statistical verbs do not, so extending the file-backed path across the rest of the API is the obvious follow-up. The deprecated tibble re-exports and the now-defunct n_fields argument suggest continued removal of the compatibility layer in the next minor release.
writeAlizer
0.0INFRA · APIS
Six months of releases and not one of them touched the scoring models
◆ Current state
writeAlizer generates predicted writing-quality scores from features produced by Coh-Metrix, ReaderBench and GAMET, downloading its trained scoring models on demand. Every release in this window — nine of them between September 2025 and February 2026 — is about that download path rather than the scoring: classed error conditions, checksum verification, an offline mode, a mockable artifact directory, and dependency reporting for the model families a user actually invokes.
◆ Where it's heading
The package is being made safe to distribute. CRAN's policy on packages that reach the internet drove the first wave — graceful failure, tests that preflight their URLs and skip, examples seeded from a local mock model — and 1.7.0 turned the accumulated fixes into structure with named error classes for each failure mode. Only 1.7.2 adds anything a user would ask for: filename handling for Coh-Metrix and GAMET outputs that arrive as paths.
◆ Prediction
With the artifact registry hardened and documented, the pressure that produced nine releases in six months should ease, and attention can return to the models themselves — the vignette on scoring-model development added in 1.7.2 hints at that. Nothing here promises new models.
Alternatives to valr and writeAlizer
Other Infra & APIs 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 valr or writeAlizer.
PINstimation
A market-microstructure toolkit that keeps adding estimators as the papers land.
nzilbb.vowels
A vowel-analysis package trimming dependencies after an email address got it archived.
emuR
The R half of the EMU speech database system, fixing what was quietly broken.
BAS
A Bayesian model-averaging package spending its 2.0 on memory, not methods.
tidyplots
tidyplots keeps rebuilding its own foundations rather than layering around them.
See all valr alternatives → · See all writeAlizer alternatives →
Recent activity from valr and writeAlizer
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 1mo agovalrInterval verbs read bigWig and bigBed files directly ⚡
- 6mo agowriteAlizerOne example rewrapped to silence a CRAN check note
- 7mo agovalrbed_slop() and bed_flank() preserve input row order
- 8mo agovalrmin_overlap introduced; C++ backend moves from Rcpp to cpp11
- 8mo agowriteAlizerFilename stems recovered from Coh-Metrix and GAMET paths
- 10mo agowriteAlizerOffline example guard, declared as no API change
- 10mo agowriteAlizerNamed error classes for every model-download failure mode
- 10mo agowriteAlizerNetwork failures degrade gracefully under CRAN policy
- 11mo agowriteAlizerwa_seed_example_models() exported and documented
- 1y agovalrTest updated for ggplot2 3.6.0
- 1y agovalrread_bigwig() switches to cpp11bigwig; read_gtf() deprecated
- 1y agovalrCRAN Rd link NOTE and maintainer email change
Frequently asked questions
What is the difference between valr and writeAlizer?
They serve adjacent needs but don't currently overlap on shipped themes. valr and writeAlizer 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 valr better than writeAlizer?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. valr and writeAlizer 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 Infra & APIs products to evaluate alongside.
What are the best alternatives to valr?
Top valr alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "valr alternatives" section above for the current picks, or visit /alternatives/valr for the full list with editorial commentary on each.
What are the best alternatives to writeAlizer?
Top writeAlizer alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "writeAlizer alternatives" section above for the current picks, or visit /alternatives/writealizer for the full list with editorial commentary on each.