distributions3
distributions3 changes hands to Achim Zeileis, and a moment calculation bug goes with it.
A side-by-side editorial comparison of climaemet and fastplyr — release velocity, themes, recent moves, and the top alternatives to consider.
climaemet added weather alerts and wildfire risk, then spent two years managing rate limits.
climaemet wraps Spain's AEMET meteorological API — station data, historical climate series, forecasts, and the plotting helpers that go with them. Its capability surface widened decisively in 1.4.0 with meteorological alerts and wildfire risk rasters. Everything since has been about surviving the API rather than extending it: multiple API keys, quota-aware key selection, and httr2 throttling pinned to AEMET's stated 40-connections-per-minute policy.
A fast dplyr stand-in that keeps finding new places to skip work entirely.
fastplyr reimplements the dplyr verbs on a faster backend, exposing f_summarise, f_mutate, f_reframe and a set of group metadata helpers alongside optimized joins and quantiles. The most recent release removes non-API C functions and raises the floor to R 4.5.0, a steep requirement that follows the C++17 requirement introduced a release earlier. The verb surface itself has been stable since 0.9.0.
climaemet wraps Spain's AEMET meteorological API — station data, historical climate series, forecasts, and the plotting helpers that go with them. Its capability surface widened decisively in 1.4.0 with meteorological alerts and wildfire risk rasters. Everything since has been about surviving the API rather than extending it: multiple API keys, quota-aware key selection, and httr2 throttling pinned to AEMET's stated 40-connections-per-minute policy.
Two forces shape this package, and neither is feature demand. The first is AEMET's own churn — new response codes, a fires endpoint that switched to six risk levels returned as named factors, municipality datasets refreshed annually. The second is the maintainer's cross-package modernization, visible here as the API key store moving to tools::R_user_dir() with automatic migration, a configurable timeout, cli messaging, and an R 4.1 floor. The 1.6.0 refactor is stated as AI-assisted, matching the maintainer's other packages.
Expect the next release to track another AEMET endpoint change rather than add a data domain; the throttling and multi-key machinery suggests quota pressure is the constraint the maintainer keeps returning to.
fastplyr reimplements the dplyr verbs on a faster backend, exposing f_summarise, f_mutate, f_reframe and a set of group metadata helpers alongside optimized joins and quantiles. The most recent release removes non-API C functions and raises the floor to R 4.5.0, a steep requirement that follows the C++17 requirement introduced a release earlier. The verb surface itself has been stable since 0.9.0.
The optimization strategy has shifted from making individual functions fast to reasoning about expressions before evaluating them — 0.9.9 began marking simple operators as group-unaware so expressions built only from them are evaluated across the whole data frame rather than per group. That is a structural bet: the package increasingly inspects what you wrote to decide how much work is actually needed. Running alongside it is a steady tightening of build requirements, with C++17, R 4.5.0 and CRAN's C API rules all landing within a year.
Expect the group-unaware classification to widen to more functions, since each addition compounds across every grouped expression, and expect the dependency floors to keep rising as the package tracks CRAN's compiled-code policy.
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 climaemet or fastplyr.
distributions3 changes hands to Achim Zeileis, and a moment calculation bug goes with it.
After two and a half years dormant, mizer shipped three major versions in seven weeks.
vellumplot tags its first release with a bet most R grammars don't make: the static figure and the widget are the same object.
vellum's bugs are now found by using it, not testing it — the downstream grammar is doing the QA.
n2kanalysis has spent eight years wiring INLA models to an S3 bucket.
A Fortran-descended optimizer got thread-safe, then found two flags that never worked.
See all climaemet alternatives → · See all fastplyr alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — r-package — within Analytics. climaemet and fastplyr 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.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. climaemet and fastplyr 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.
Top climaemet alternatives in Analytics are ranked by recent ship velocity. Browse the "climaemet alternatives" section above for the current picks, or visit /alternatives/climaemet for the full list with editorial commentary on each.
Top fastplyr alternatives in Analytics are ranked by recent ship velocity. Browse the "fastplyr alternatives" section above for the current picks, or visit /alternatives/fastplyr for the full list with editorial commentary on each.