osmdata
osmdata keeps tightening its Overpass query surface, breaking small things to get types right.
A side-by-side editorial comparison of rvest and timetk — release velocity, themes, recent moves, and the top alternatives to consider.
rvest grew a real browser, turning a static scraper into a dynamic one.
rvest is the tidyverse's HTML scraping package. The 1.0.0 line rebuilt table parsing to mimic how browsers actually read tables, and 1.0.4 added read_html_live(), which drives a headless browser so JavaScript-rendered pages can be scraped at all. 1.0.5 is consolidation on that newer path.
timetk swallowed anomalize whole, then went quiet for two years
timetk handles time series wrangling, visualization, and feature engineering in a tidyverse idiom. Its defining recent move was absorbing the anomalize package outright in 2.9.0, bringing anomaly detection, cleaning, and the associated plots inside timetk rather than leaving them in a sibling package. Development then paused for nearly two years before 2.9.1, a robustness and documentation release.
rvest is the tidyverse's HTML scraping package. The 1.0.0 line rebuilt table parsing to mimic how browsers actually read tables, and 1.0.4 added read_html_live(), which drives a headless browser so JavaScript-rendered pages can be scraped at all. 1.0.5 is consolidation on that newer path.
The package has split into two modes: fast static parsing for ordinary documents, and a live browser session for client-rendered ones. Recent effort concentrates on hardening the live path, where page navigation and interaction bugs surface that never existed in static parsing.
Expect further fixes and documentation around read_html_live() as more scraping targets move rendering to the client.
timetk handles time series wrangling, visualization, and feature engineering in a tidyverse idiom. Its defining recent move was absorbing the anomalize package outright in 2.9.0, bringing anomaly detection, cleaning, and the associated plots inside timetk rather than leaving them in a sibling package. Development then paused for nearly two years before 2.9.1, a robustness and documentation release.
The trajectory before the pause was consolidation: fold in adjacent functionality, then make the visualization layer handle many series at once via trelliscopejs, then broaden feature generation with tk_tsfeatures(). The recent release works on the least glamorous layer — internal generics so date parsing and sequence generation behave consistently across Date, POSIXct, hms, yearmon, and yearqtr — which is the kind of foundation work a package does when it has accumulated too many special cases. The long gap and the CI-refresh content suggest maintenance attention rather than a new direction.
The stated gap is the unimplemented twitter method for anomalize(), which is the one concrete outstanding item the release notes name; beyond that the recent work points to consolidation rather than expansion.
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 rvest or timetk.
osmdata keeps tightening its Overpass query surface, breaking small things to get types right.
posterior keeps deepening two things: the rvar type and Pareto-based diagnostics.
rredlist threw out its species-centric API in 1.0.0 and rebuilt around assessments.
esquisse's 1.0 turned a point-and-click addin into embeddable Shiny modules.
mlr3proba is shedding weight as its survival work moves into sibling packages
mlr3viz keeps the ecosystem's plots working while the plots themselves move out
See all rvest alternatives → · See all timetk alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. rvest and timetk 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. rvest and timetk 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 rvest alternatives in Analytics are ranked by recent ship velocity. Browse the "rvest alternatives" section above for the current picks, or visit /alternatives/rvest for the full list with editorial commentary on each.
Top timetk alternatives in Analytics are ranked by recent ship velocity. Browse the "timetk alternatives" section above for the current picks, or visit /alternatives/timetk for the full list with editorial commentary on each.