rollupTree
The recursive-computation engine under massProps grows the accessors its consumer needed
A side-by-side editorial comparison of formr and rstudio.prefs — release velocity, themes, recent moves, and the top alternatives to consider.
formr's R client reached CRAN and moved its recommended path to the v1 REST API.
formr is the R-side client for formr.org, the open study framework used to run longitudinal and experience-sampling questionnaires. In May it reached CRAN for the first time, released in step with formr.org server v1.0.0, and the formr_api_* family built on the server's RESTful surface became the supported entry point. The three releases since have been repair work on the paths that move rendered output and API results.
Four years dormant, rstudio.prefs returns under a new maintainer.
The package scripts RStudio's own settings — preferences, secondary repositories, keyboard shortcuts — as code you can drop into a project or an onboarding doc. After 0.1.9 in July 2022 it went quiet for four years. 0.2.0 ends that with a maintainer handoff from Daniel D. Sjoberg to S.A. van der Wulp, a shortcut-removal path, and a fix for a corrupted addins.json entry that made reassigned shortcuts fail silently.
formr is the R-side client for formr.org, the open study framework used to run longitudinal and experience-sampling questionnaires. In May it reached CRAN for the first time, released in step with formr.org server v1.0.0, and the formr_api_* family built on the server's RESTful surface became the supported entry point. The three releases since have been repair work on the paths that move rendered output and API results.
The direction is consolidation around the v1 API while the legacy Classic path is left running but demoted in the vignette. The complication is that CRAN's requirements and the OpenCPU server's requirements pull against each other: CRAN review pushed rendering into tempdir() with random filenames, which broke rforms.org because the server fetches a fixed knit.html, and 1.1.2 had to put it back. The 1.2.0 note describes the same write-directory problem being solved in an OpenCPU-aware way rather than reverted, alongside making dependencies installable under WASM.
Two of the last three releases were regressions in the render path, so the OpenCPU-aware write directory in 1.2.0 is the change most likely to need follow-up. The Classic formr_results() path remains in the package with no removal date announced, and nothing in these entries indicates when that ends.
The package scripts RStudio's own settings — preferences, secondary repositories, keyboard shortcuts — as code you can drop into a project or an onboarding doc. After 0.1.9 in July 2022 it went quiet for four years. 0.2.0 ends that with a maintainer handoff from Daniel D. Sjoberg to S.A. van der Wulp, a shortcut-removal path, and a fix for a corrupted addins.json entry that made reassigned shortcuts fail silently.
The through-line is teaching every setter how to unset. Secondary repositories got NULL removal back in 0.1.6; 0.2.0 extends the same convention to keyboard shortcuts. Most of the rest of 0.2.0 is arrears — a stale documentation URL that hid preferences such as enable_splash_screen, a deprecated purrr::update_list() call, and check_shortcut_consistency() erroring early on an unknown name.
With a new maintainer and refreshed GitHub Actions, the near-term work is likely more catch-up of the same kind: remaining deprecated dependencies and the preference list that fetch_rstudio_prefs() reads from RStudio's docs. Nothing in these notes points past RStudio settings as the scope.
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 formr or rstudio.prefs.
The recursive-computation engine under massProps grows the accessors its consumer needed
A mass-properties rollup spends a year on documentation and follows its sibling's API
Six months of releases and not one of them touched the scoring models
A cognitive-science sampling package ships once, then goes quiet for eighteen months
A Bayesian volatility sampler in its maintenance decade, paying for its own speed
A black-box interpreter reaches CRAN, then learns multi-class and survival responses
See all formr alternatives → · See all rstudio.prefs alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — r-packages — within Infra & APIs. rstudio.prefs is currently shipping more aggressively (velocity 2.5 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.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. rstudio.prefs is currently shipping more aggressively (velocity 2.5 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 Infra & APIs products to evaluate alongside.
Top formr alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "formr alternatives" section above for the current picks, or visit /alternatives/formr for the full list with editorial commentary on each.
Top rstudio.prefs alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "rstudio.prefs alternatives" section above for the current picks, or visit /alternatives/rstudio-prefs for the full list with editorial commentary on each.