tidytlg
A tables-listings-graphs package that reached CRAN and then went quiet.
Comparison · Analytics
datefixR vs gigs
A side-by-side editorial comparison of datefixR and gigs — release velocity, themes, recent moves, and the top alternatives to consider.
Shared themes:r-package
datefixR vs gigs: at a glance
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.
What is gigs?
gigs redesigned its whole conversion API for rOpenSci, then spent three releases getting the docs to build.
gigs implements international newborn and infant growth standards — INTERGROWTH-21st, WHO — converting anthropometric measurements to z-scores and centiles and classifying growth outcomes. The 0.5.0 release rewrote the public API around rOpenSci review feedback; the two releases after it change no code at all, existing purely to get the documentation site building.
datefixR vs gigs: editorial side-by-side
datefixR
0.0ANALYTICS
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.
gigs
0.0ANALYTICS
gigs redesigned its whole conversion API for rOpenSci, then spent three releases getting the docs to build.
◆ Current state
gigs implements international newborn and infant growth standards — INTERGROWTH-21st, WHO — converting anthropometric measurements to z-scores and centiles and classifying growth outcomes. The 0.5.0 release rewrote the public API around rOpenSci review feedback; the two releases after it change no code at all, existing purely to get the documentation site building.
◆ Where it's heading
The package has moved from vector-in, vector-out conversion helpers to a data.frame-oriented interface with a single classify_growth() entry point that computes whatever outcomes the supplied columns allow. That is a shift from library to tool — the user describes their data rather than picking the right function. The trailing releases suggest the code is settled and the remaining work is packaging and discoverability.
◆ Prediction
With the API rewrite absorbed and hosting moved to rOpenSci, the next substantive release should add growth standards or outcomes rather than reshape the interface again.
Alternatives to datefixR and gigs
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 gigs.
Tplyr
Tplyr made clinical summary tables explain where every number came from.
rlistings
Clinical listings that keep inheriting their hardest problem — pagination — from the layer below.
hoardr
A cache-directory helper that has shipped nothing but CRAN-triggered patches for seven years.
riem
A weather-data client that keeps rewriting its HTTP layer while slowly tightening its API.
datasetjson
datasetjson rebuilt its object model to track the CDISC Dataset-JSON 1.1 schema.
See all datefixR alternatives → · See all gigs alternatives →
Recent activity from datefixR and gigs
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 3mo agodatefixRRust rewrite regressions repaired, silent NA casting stopped
- 11mo agodatefixRParsing core rewritten in Rust for a 300x speedup ⚡
- 1y agogigsDocs and Zenodo archiving
- 1y agogigsDocs-only release; nothing changed internally
- 1y agogigsConversion API rewritten around data frames and classify_growth() ⚡
- 1y agodatefixRIndonesian month names and translations added
- 2y agogigsDocumentation fixes for autotest compliance
- 2y agogigsINTERGROWTH-21st fetal standards and input validation
- 2y agodatefixR'ene' and 'ener' recognized as January
- 2y agogigsPatch release with documentation update
- 3y agodatefixRRussian localization, Roman numeral months, Windows freeze fix
- 3y agodatefixRExcel leap-year offset and single-digit day fixes
Frequently asked questions
What is the difference between datefixR and gigs?
Both compete on the same themes — r-package — within Analytics. datefixR and gigs 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 datefixR better than gigs?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. datefixR and gigs 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 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 gigs?
Top gigs alternatives in Analytics are ranked by recent ship velocity. Browse the "gigs alternatives" section above for the current picks, or visit /alternatives/gigs for the full list with editorial commentary on each.