rollupTree
The recursive-computation engine under massProps grows the accessors its consumer needed
Comparison · Infra & APIs
anticlust vs rstudio.prefs
A side-by-side editorial comparison of anticlust and rstudio.prefs — release velocity, themes, recent moves, and the top alternatives to consider.
anticlust vs rstudio.prefs: at a glance
What is anticlust?
Anticlustering keeps absorbing constraints — must-link, cannot-link, blocks, missing data
anticlust partitions a set of items into groups that are as similar to each other as possible — assembling matched stimulus sets, balanced experimental conditions, comparable teaching groups. The current surface is one function, anticlustering(), with a growing list of things it will honour: must-link and cannot-link constraints, categorical variables as factors, NAs, blocking by a categorical level, and a choice among exact solvers and heuristics.
What is rstudio.prefs?
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.
anticlust vs rstudio.prefs: editorial side-by-side
anticlust
0.0INFRA · APIS
Anticlustering keeps absorbing constraints — must-link, cannot-link, blocks, missing data
◆ Current state
anticlust partitions a set of items into groups that are as similar to each other as possible — assembling matched stimulus sets, balanced experimental conditions, comparable teaching groups. The current surface is one function, anticlustering(), with a growing list of things it will honour: must-link and cannot-link constraints, categorical variables as factors, NAs, blocking by a categorical level, and a choice among exact solvers and heuristics.
◆ Where it's heading
Two years of releases have gone almost entirely into constraint handling and input tolerance rather than new objectives. The methods list grew by absorbing outside work — the three-phase search of Yang et al. contributed by an external author, a 2PML heuristic for must-link problems, a Gurobi backend for the exact formulations. Meanwhile categories_to_binary() has been rewritten twice, which is where the recent bugs have come from.
◆ Prediction
The constraint types now interact combinatorially — blocks, must-link, cannot-link, missing values and each objective — and the last two releases were both regressions in the encoding layer underneath them. Consolidating that layer is the more likely next move than another solver.
rstudio.prefs
2.5INFRA · APIS
Four years dormant, rstudio.prefs returns under a new maintainer.
◆ Current state
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.
◆ Where it's heading
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.
◆ Prediction
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.
Alternatives to anticlust and rstudio.prefs
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 anticlust or rstudio.prefs.
massProps
A mass-properties rollup spends a year on documentation and follows its sibling's API
writeAlizer
Six months of releases and not one of them touched the scoring models
samplr
A cognitive-science sampling package ships once, then goes quiet for eighteen months
stochvol
A Bayesian volatility sampler in its maintenance decade, paying for its own speed
midr
A black-box interpreter reaches CRAN, then learns multi-class and survival responses
See all anticlust alternatives → · See all rstudio.prefs alternatives →
Recent activity from anticlust and rstudio.prefs
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 8h agorstudio.prefsShortcut removal, an addins.json fix, and a new maintainer
- 4mo agoanticlustOne-hot encoding regression from 0.8.13 reverted
- 8mo agoanticlustblocks argument applies anticlustering level by level
- 9mo agoanticlustMissing values, factor columns, and the three-phase search
- 1y agoanticlustEdge cases in the previous release's cannot-link handling
- 1y agoanticlustVector cannot-link constraints skip the solver entirely
- 1y agoanticlustUncaught test error flagged by CRAN additional checks
- 4y agorstudio.prefsPreferences now read and written through rstudioapi
- 4y agorstudio.prefsConfig files left alone when nothing would change
- 4y agorstudio.prefsSecondary repositories can be deleted again
- 4y agorstudio.prefsRepository removal via NULL; config path helpers exported
- 5y agorstudio.prefsDocumentation, error messages, and array-type caution
Frequently asked questions
What is the difference between anticlust and rstudio.prefs?
They serve adjacent needs but don't currently overlap on shipped themes. 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.
Is anticlust better than rstudio.prefs?
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.
What are the best alternatives to anticlust?
Top anticlust alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "anticlust alternatives" section above for the current picks, or visit /alternatives/anticlust for the full list with editorial commentary on each.
What are the best alternatives to rstudio.prefs?
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.