← Back to home
Comparison · Analytics

datefixR vs ggsurvfit

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

datefixR vs ggsurvfit: at a glance

FeaturedatefixRggsurvfit
SectorAnalyticsAnalytics
Velocity score0.02.5
Sparks · 30d00
Top themesdate-parsing, rust, data-cleaning, localizationsurvival-analysis, ggplot2, competing-risks, clinical-plots
Last editorial update57m ago3h ago
WebsiteVisit →Visit →

What is datefixR?

The messy-date parser rewrote its core in Rust and came out 300x faster.

datefixR standardizes inconsistently formatted dates — the kind that arrive from spreadsheets and hand-entered clinical or survey data, with mixed separators, ambiguous orders, missing components, and month names in whatever language the source used. Version 2.0.0 rewrote the parsing core in Rust, reporting over 300x throughput against previous versions through fastpath handling of common formats and parallel column processing via a cores argument. Version 2.0.1 then spent itself cleaning up after that rewrite, restoring ordinal indicator support, stopping malformed dates from being silently cast to NA, and reinstating error messages that had gone missing.

Read the full datefixR trajectory →

What is ggsurvfit?

ggsurvfit is in correctness-and-compatibility mode, not feature mode.

The package draws survival and cumulative-incidence curves on a ggplot2 grammar, with risk tables, p-values and quantile annotations. Recent releases are entirely fixes and upstream tracking: ggplot2 v4.0.0 compatibility in 2025, and a 2026 patch correcting a Gray-test p-value that could be reported for the wrong competing event.

Read the full ggsurvfit trajectory →

datefixR vs ggsurvfit: editorial side-by-side

D
datefixR
ANALYTICS
0.0

The messy-date parser rewrote its core in Rust and came out 300x faster.

◆ Current state

datefixR standardizes inconsistently formatted dates — the kind that arrive from spreadsheets and hand-entered clinical or survey data, with mixed separators, ambiguous orders, missing components, and month names in whatever language the source used. Version 2.0.0 rewrote the parsing core in Rust, reporting over 300x throughput against previous versions through fastpath handling of common formats and parallel column processing via a cores argument. Version 2.0.1 then spent itself cleaning up after that rewrite, restoring ordinal indicator support, stopping malformed dates from being silently cast to NA, and reinstating error messages that had gone missing.

◆ Where it's heading

Two long arcs meet here. The first is localization: Russian, Indonesian, German, Spanish month abbreviations, and experimental Roman numeral months accumulated release by release, with full translation of user-facing messages treated as a goal rather than a bonus. The second is the migration off R for the parsing hot path — internals began moving to C++ around 1.3.1 before the Rust rewrite replaced that work entirely. The 2.0.1 regressions show the cost of that move, since behavior that was implicit in the R implementation had to be re-specified.

◆ Prediction

The Rust core is one release into stabilization and 2.0.1 was entirely regression repair, so expect further correctness fixes against pre-2.0.0 behavior before any new format support lands.

G
ggsurvfit
ANALYTICS
2.5

ggsurvfit is in correctness-and-compatibility mode, not feature mode.

◆ Current state

The package draws survival and cumulative-incidence curves on a ggplot2 grammar, with risk tables, p-values and quantile annotations. Recent releases are entirely fixes and upstream tracking: ggplot2 v4.0.0 compatibility in 2025, and a 2026 patch correcting a Gray-test p-value that could be reported for the wrong competing event.

◆ Where it's heading

The feature surface settled around 1.0.0, when risk-table alignment was exported and colour and linetype defaults became configurable. Since then the work is keeping pace with survival, ggplot2 and tidycmprsk changes, and closing cases where the plotted curve and the annotation disagreed — the p-value matched by position rather than name, confidence limits swapped for multi-state models, quantiles read off a plateau.

◆ Prediction

Expect the next release to track upstream survival or ggplot2 changes rather than add plotting features; the CDISC censoring convention adopted in Surv_CNSR() suggests further alignment with clinical data standards is the likelier direction.

Alternatives to datefixR and ggsurvfit

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 datefixR or ggsurvfit.

See all datefixR alternatives → · See all ggsurvfit alternatives →

Recent activity from datefixR and ggsurvfit

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

  1. 20d agoggsurvfitGray-test p-values matched to the plotted outcome by name
  2. 3mo agodatefixRRust rewrite regressions repaired, silent NA casting stopped
  3. 10mo agoggsurvfitggplot2 v4.0.0 compatibility and multi-state CI label fix
  4. 11mo agodatefixRParsing core rewritten in Rust for a 300x speedup
  5. 1y agodatefixRIndonesian month names and translations added
  6. 2y agoggsurvfitNegative follow-up times and a cloglog transformation
  7. 2y agodatefixR'ene' and 'ener' recognized as January
  8. 2y agoggsurvfitAesthetic defaults become switchable and alignment is exported
  9. 2y agoggsurvfitConfidence limits corrected for monotonicity-reversing transforms
  10. 3y agodatefixRRussian localization, Roman numeral months, Windows freeze fix
  11. 3y agoggsurvfitGlue syntax in risk tables and coxph model support
  12. 3y agodatefixRExcel leap-year offset and single-digit day fixes

Frequently asked questions

What is the difference between datefixR and ggsurvfit?

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

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. ggsurvfit 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 Analytics products to evaluate alongside.

What are the best alternatives to datefixR?

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

What are the best alternatives to ggsurvfit?

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