← Back to home
Comparison · Analytics

collinear vs gghighlight

A side-by-side editorial comparison of collinear and gghighlight — release velocity, themes, recent moves, and the top alternatives to consider.

collinear vs gghighlight: at a glance

Featurecollineargghighlight
SectorAnalyticsAnalytics
Velocity score0.00.0
Sparks · 30d00
Top themesmulticollinearity, variable selection, vif, breaking changesggplot2, data-visualisation, ggplot-extension, upstream-compat
Last editorial update8h ago1h ago
WebsiteVisit →Visit →

What is collinear?

collinear has broken its API twice to stop making the user pick thresholds.

collinear removes multicollinearity from predictor sets through pairwise correlation and VIF filtering, with a preference order deciding which variable survives each conflict. Two major versions in thirteen months each rewrote the interface: 2.0.0 extended every function to any combination of categorical and numeric responses and predictors, and 3.0.0 moved to multiple responses, restructured the output into classed objects, and made both filtering thresholds adaptive by default. Version 3.0.1 is the first release since that is purely repair.

Read the full collinear trajectory →

What is gghighlight?

A single-purpose ggplot2 extension that has spent six years tracking ggplot2 instead of growing.

gghighlight adds one verb to ggplot2: highlight the series matching a predicate and grey out the rest, with unhighlighted_params controlling how the shadowed layer renders and calculate_per_facet deciding whether the predicate evaluates within facets. The API settled at 0.2.0; the 0.5.0 release supports ggplot2 v4.0 including its ink and paper theme elements, and finally deletes gghighlight_point() and gghighlight_line().

Read the full gghighlight trajectory →

collinear vs gghighlight: editorial side-by-side

C
collinear
ANALYTICS
0.0

collinear has broken its API twice to stop making the user pick thresholds.

◆ Current state

collinear removes multicollinearity from predictor sets through pairwise correlation and VIF filtering, with a preference order deciding which variable survives each conflict. Two major versions in thirteen months each rewrote the interface: 2.0.0 extended every function to any combination of categorical and numeric responses and predictors, and 3.0.0 moved to multiple responses, restructured the output into classed objects, and made both filtering thresholds adaptive by default. Version 3.0.1 is the first release since that is purely repair.

◆ Where it's heading

The through-line is removing decisions the user was never well placed to make. Preference-order functions were renamed twice — first onto a metric-and-model scheme in 2.0.0, then onto a response-type scheme in 3.0.0 — and f_auto() picks one when none is given; target encoding went from automatic to opt-in; max_cor and max_vif now default to NULL and trigger a data-driven threshold derived from the 75th percentile of pairwise correlations through a sigmoid and a fitted correlation-to-VIF mapping. Each change is defensible and each one broke callers, which is the cost of this approach.

◆ Prediction

3.0.1 moved the example datasets out into a separate spatialData package and fixed four crashes rather than adding anything, so the next release is most likely more consolidation on the 3.0 surface than a fourth interface.

G
gghighlight
ANALYTICS
0.0

A single-purpose ggplot2 extension that has spent six years tracking ggplot2 instead of growing.

◆ Current state

gghighlight adds one verb to ggplot2: highlight the series matching a predicate and grey out the rest, with unhighlighted_params controlling how the shadowed layer renders and calculate_per_facet deciding whether the predicate evaluates within facets. The API settled at 0.2.0; the 0.5.0 release supports ggplot2 v4.0 including its ink and paper theme elements, and finally deletes gghighlight_point() and gghighlight_line().

◆ Where it's heading

Two threads run through the history. One is a slow deprecation, from soft-deprecating the geom-specific functions at 0.1.0, to defunct at 0.3.0, to removed at 0.5.0 — a five-year removal cycle. The other is compatibility work: purrr 1.0.0, dplyr's across() deprecation, ggplot2 3.4.0, then 4.0. Genuine feature additions are rare and small, with line_label_type at 0.4.0 the last one. Note that 0.3.2's notes restate 0.3.1's n() item, so adjacent tags here overlap rather than each describing distinct work.

◆ Prediction

The next release most likely absorbs further ggplot2 4.x changes, given that is what triggered the last three. Nothing in the entries points to a new highlighting capability.

Alternatives to collinear and gghighlight

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 collinear or gghighlight.

See all collinear alternatives → · See all gghighlight alternatives →

Recent activity from collinear and gghighlight

Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.

  1. 3mo agocollinearNamespace, NA and sf fixes; example data moves to spatialData
  2. 8mo agocollinearAdaptive thresholds, multi-response support and a new output class
  3. 1y agogghighlightggplot2 v4.0 support; geom-specific functions removed
  4. 1y agocollinearCategorical responses, f_auto() defaults and future-based parallelism
  5. 2y agogghighlightTest expectations updated for upcoming ggplot2
  6. 3y agogghighlightline_label_type adds geomtextpath and second-axis labelling
  7. 4y agogghighlightDeprecated dplyr::across() usage removed
  8. 5y agogghighlightExplicit NULL in unhighlighted_params preserved; aesthetic name clash fixed
  9. 5y agogghighlightDiscrete-scale labels and n() predicates

Frequently asked questions

What is the difference between collinear and gghighlight?

They serve adjacent needs but don't currently overlap on shipped themes. collinear and gghighlight 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 collinear better than gghighlight?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. collinear and gghighlight 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 collinear?

Top collinear alternatives in Analytics are ranked by recent ship velocity. Browse the "collinear alternatives" section above for the current picks, or visit /alternatives/collinear for the full list with editorial commentary on each.

What are the best alternatives to gghighlight?

Top gghighlight alternatives in Analytics are ranked by recent ship velocity. Browse the "gghighlight alternatives" section above for the current picks, or visit /alternatives/gghighlight for the full list with editorial commentary on each.