discrim
discrim settled into a thin engine shim after handing its model definitions to parsnip.
Comparison · Analytics
rvest vs tune
A side-by-side editorial comparison of rvest and tune — release velocity, themes, recent moves, and the top alternatives to consider.
rvest vs tune: at a glance
What is rvest?
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.
What is tune?
tune extends tuning past the model itself to postprocessors, and adds a second parallel backend
tune runs hyperparameter search for tidymodels. Version 2.0.0 rewrote tune_grid() to make postprocessing tunable alongside preprocessing and the model, changed the .config naming scheme to match, and added mirai as a parallel backend next to future. Version 2.1.0 followed with quantile regression support and a replacement Gaussian process engine.
rvest vs tune: editorial side-by-side
rvest
0.0ANALYTICS
rvest grew a real browser, turning a static scraper into a dynamic one.
◆ Current state
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.
◆ Where it's heading
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.
◆ Prediction
Expect further fixes and documentation around read_html_live() as more scraping targets move rendering to the client.
tune
0.0ANALYTICS
tune extends tuning past the model itself to postprocessors, and adds a second parallel backend
◆ Current state
tune runs hyperparameter search for tidymodels. Version 2.0.0 rewrote tune_grid() to make postprocessing tunable alongside preprocessing and the model, changed the .config naming scheme to match, and added mirai as a parallel backend next to future. Version 2.1.0 followed with quantile regression support and a replacement Gaussian process engine.
◆ Where it's heading
Two migrations run through this timeline. The tunable surface keeps widening - first censored regression as a mode, then postprocessors via tailor - so that a candidate is now a preprocessor, model and postprocessor triple rather than just a model. The parallel story has moved from foreach to future and now to mirai, each step deprecating the last. Neither is finished.
◆ Prediction
Expect the foreach path to be removed outright, and the postprocessing surface to grow as tailor gains more steps; the GauPro switch will likely need follow-up as its behavior differs from the old engine.
Alternatives to rvest and tune
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 tune.
dbparser
dbparser shed its database and CSV writers to become just a DrugBank parser.
desirability2
desirability2 is making multi-metric model selection a first-class tidymodels step.
crosstalk
crosstalk is frozen infrastructure: four releases in five years, mostly CRAN upkeep.
cmdstanr
cmdstanr keeps adding fast approximations beside full HMC, and fighting Windows toolchains.
comtradr
comtradr's 1.0 line is a long tail of patches against a brittle UN trade API.
Recent activity from rvest and tune
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 3mo agotuneQuantile regression tuning; Bayesian search moves to GauPro
- 9mo agotuneFixes int_pctl() with future parallelism on last_fit()
- 11mo agotunePostprocessors become tunable; mirai joins future as a backend ⚡
- 11mo agotuneDevelopment snapshot re-enabling skipped tests
- 11mo agorvestrvest 1.0.5 fixes stale nodes after click navigation in LiveHTML
- 1y agotuneWarns on foreach parallelism; space-filling grids by default
- 2y agotuneFixes parallel tuning errors under multisession plans
- 2y agorvestrvest 1.0.4 scrapes JavaScript pages via a live browser session ⚡
- 3y agorvestrvest 1.0.3 re-documents to fix .Rd HTML issues
- 4y agorvestrvest 1.0.2 returns empty tibbles for empty tables
- 5y agorvestrvest 1.0.1 parses blank rowspan and colspan as 1
- 5y agorvestrvest 1.0.0 rewrites table parsing to match browser behaviour
Frequently asked questions
What is the difference between rvest and tune?
They serve adjacent needs but don't currently overlap on shipped themes. rvest and tune 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 rvest better than tune?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. rvest and tune 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 rvest?
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.
What are the best alternatives to tune?
Top tune alternatives in Analytics are ranked by recent ship velocity. Browse the "tune alternatives" section above for the current picks, or visit /alternatives/tune for the full list with editorial commentary on each.