pins
pins keeps adding a storage backend per release while retiring its original API
Comparison · Analytics
Displayr vs tune
A side-by-side editorial comparison of Displayr and tune — release velocity, themes, recent moves, and the top alternatives to consider.
Displayr vs tune: at a glance
What is Displayr?
Chat is being made legible while the survey-analysis core picks up the fundamentals it lacked.
Displayr is shipping on two fronts at a steady, unhurried cadence. The AI assistant is being made auditable rather than more capable — a context pill showing exactly what a prompt will send, a change summary listing every item Chat added, edited or deleted, and an Explain This button that routes errors and warnings into Chat with context attached. Separately the document core is filling in fundamentals: controls that stay synced across pages and page masters, rolling averages computed on date-keyed tables, browser-style back and forward navigation, and templates that can be saved as folder-scoped defaults.
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.
Displayr vs tune: editorial side-by-side
Displayr
5.0ANALYTICS
Chat is being made legible while the survey-analysis core picks up the fundamentals it lacked.
◆ Current state
Displayr is shipping on two fronts at a steady, unhurried cadence. The AI assistant is being made auditable rather than more capable — a context pill showing exactly what a prompt will send, a change summary listing every item Chat added, edited or deleted, and an Explain This button that routes errors and warnings into Chat with context attached. Separately the document core is filling in fundamentals: controls that stay synced across pages and page masters, rolling averages computed on date-keyed tables, browser-style back and forward navigation, and templates that can be saved as folder-scoped defaults.
◆ Where it's heading
The Chat work reads as a deliberate answer to the trust problem with AI in analyst tools — every release makes what the assistant touched inspectable rather than expanding what it can do unprompted. The other track is closing gaps a long-standing survey analysis platform accumulates, with the default-template mechanic notable for scoping defaults by Cloud Drive folder, which turns a personal preference into an organizational standard. Neither track has produced a directional move in this window.
◆ Prediction
Expect the transparency pattern to extend to Chat actions that modify data rather than layout, since the change summary establishes the mechanism. Folder-scoped defaults look like the start of broader template governance.
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 Displayr 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 Displayr or tune.
tsibble
tsibble shipped one release in five and a half years - the data structure is finished
yardstick
yardstick made fairness metrics a first-class part of tidymodels evaluation
leaflet
leaflet relicensed to MIT and finished migrating off R's retired spatial stack
ggpubr
ggpubr reached 1.0.0 with p-value formatting presets for specific journals
bigrquery
bigrquery went MIT, then handed its slowest path to the BigQuery Storage API
See all Displayr alternatives → · See all tune alternatives →
Recent activity from Displayr and tune
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 19h agoDisplayrUse the Same Control Across Multiple Pages and Page Masters
- 19h agoDisplayrRolling Averages Computed Automatically on Tables
- 16d agoDisplayrExplain This — AI help for errors & warnings
- 16d agoDisplayrBack and Forward Buttons for Navigation
- 16d agoDisplayrSave Templates as Default Visualizations
- 1mo agoDisplayrMore transparency when working with Chat
- 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
- 1y agotuneWarns on foreach parallelism; space-filling grids by default
- 2y agotuneFixes parallel tuning errors under multisession plans
Frequently asked questions
What is the difference between Displayr and tune?
They serve adjacent needs but don't currently overlap on shipped themes. Displayr is currently shipping more aggressively (velocity 5.0 vs 0.0), with 0 editorial sparks in the last 30 days against 0. See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.
Is Displayr better than tune?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Displayr is currently shipping more aggressively (velocity 5.0 vs 0.0), with 0 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other Analytics products to evaluate alongside.
What are the best alternatives to Displayr?
Top Displayr alternatives in Analytics are ranked by recent ship velocity. Browse the "Displayr alternatives" section above for the current picks, or visit /alternatives/displayr 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.