Traefik
Traefik's 2.11 line spends August fixing the names it generates for Kubernetes resources.
Comparison · Infra & APIs
hereR vs valr
A side-by-side editorial comparison of hereR and valr — release velocity, themes, recent moves, and the top alternatives to consider.
hereR vs valr: at a glance
What is hereR?
An R client for HERE's location APIs, shaped almost entirely by what the vendor exposes next.
hereR wraps HERE's routing, isoline, traffic, weather and geocoding endpoints for R, returning sf objects. Development is steady and reactive: each release either adopts a transport mode, parameter or API version HERE has newly made available, or corrects a rate limit that was producing 429 errors in practice. The current release adds speed-limit control and five more isoline transport modes.
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.
hereR vs valr: editorial side-by-side
hereR
0.0INFRA · APIS
An R client for HERE's location APIs, shaped almost entirely by what the vendor exposes next.
◆ Current state
hereR wraps HERE's routing, isoline, traffic, weather and geocoding endpoints for R, returning sf objects. Development is steady and reactive: each release either adopts a transport mode, parameter or API version HERE has newly made available, or corrects a rate limit that was producing 429 errors in practice. The current release adds speed-limit control and five more isoline transport modes.
◆ Where it's heading
Two threads run through the whole history. One is coverage — new modes, tolls and currency, arrival times, speed limits — arriving in the package shortly after they appear in HERE's API. The other is defensive operational tuning, with request rates repeatedly lowered below HERE's documented limits because the documented limits do not hold up. 1.0.0 was the one moment the package had to move rather than choose, migrating traffic to v7 and weather to v3 and breaking three functions' output in the process.
◆ Prediction
Expect the next release to enable whatever HERE exposes next in routing or isolines, and to keep adjusting request rates empirically; the package's own design appears settled.
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.
Alternatives to hereR and valr
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 hereR or valr.
NGINX
nginx returns to feature work with PROXY v2 upstream writes, and quietly adds JSON to core.
ESPHome
ESPHome closes the 2026.8 cycle, but the release body is a bare link to the real notes.
vcfR
A genomics workhorse whose visible release feed stops dead in mid-2020.
dialr
The R phone-number package stopped only parsing numbers and started asking them where they are.
ggVennDiagram
A Venn diagram package whose public release notes say almost nothing — including about its copyright cleanup.
Recent activity from hereR and valr
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 1mo agovalrInterval verbs read bigWig and bigBed files directly ⚡
- 7mo agovalrbed_slop() and bed_flank() preserve input row order
- 8mo agovalrmin_overlap introduced; C++ backend moves from Rcpp to cpp11
- 1y agovalrTest updated for ggplot2 3.6.0
- 1y agohereRSpeed limits and five more isoline transport modes
- 1y agovalrread_bigwig() switches to cpp11bigwig; read_gtf() deprecated
- 1y agohereRPedestrian consumption model dropped; route request rate lowered
- 1y agovalrCRAN Rd link NOTE and maintainer email change
- 2y agohereRTraffic v7 and Weather v3 migration breaks three functions
- 3y agohereRResubmission after CRAN archival over an undeliverable email
- 4y agohereRToll costs and currency selection arrive in routing
- 4y agohereRArrival-time routing enabled; failed requests report their endpoint
Frequently asked questions
What is the difference between hereR and valr?
They serve adjacent needs but don't currently overlap on shipped themes. hereR and valr 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 hereR better than valr?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. hereR and valr 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 hereR?
Top hereR alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "hereR alternatives" section above for the current picks, or visit /alternatives/herer for the full list with editorial commentary on each.
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.