← Back to home
Comparison · Analytics

fracture vs healthyR.data

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

fracture vs healthyR.data: at a glance

FeaturefracturehealthyR.data
SectorAnalyticsAnalytics
Velocity score0.00.0
Sparks · 30d00
Top themesnumeric formatting, fractions, utility package, maintenancer-package, healthcare-data, cms, api-client
Last editorial update5h ago2h ago
WebsiteVisit →Visit →

What is fracture?

fracture solved decimal-to-fraction conversion years ago and now only answers to CRAN.

A single-purpose package converting decimals to fractions, with a matrix form and a Unicode pretty-printer. The functional work finished in 2021-2022: an explicit denom argument, named-argument-only calling, sensible denominators at 0 and 1, and NA and Inf handled rather than erroring. The only release since is a four-year-later removal of a C++11 system requirement that R's C++17 default made redundant.

Read the full fracture trajectory →

What is healthyR.data?

From a bundled hospital dataset to a live CMS API client.

healthyR.data supplies the data layer for the healthyverse packages. It began by shipping hospital data inside the package and now fetches from CMS and provider endpoints at call time through get_cms_meta_data(), fetch_cms_data(), and their provider counterparts. The most recent release is a single httr2 compatibility fix.

Read the full healthyR.data trajectory →

fracture vs healthyR.data: editorial side-by-side

F
fracture
ANALYTICS
0.0

fracture solved decimal-to-fraction conversion years ago and now only answers to CRAN.

◆ Current state

A single-purpose package converting decimals to fractions, with a matrix form and a Unicode pretty-printer. The functional work finished in 2021-2022: an explicit denom argument, named-argument-only calling, sensible denominators at 0 and 1, and NA and Inf handled rather than erroring. The only release since is a four-year-later removal of a C++11 system requirement that R's C++17 default made redundant.

◆ Where it's heading

This is a completed utility. Its arc ran from correctness — floating-point rounding, exhaustive tests across millions of fractions — through API tightening, to edge-case tolerance, and then stopped. The 2026 release contains no user-visible change at all; it exists because CRAN's toolchain moved, which is the characteristic maintenance mode of a small package that does one thing correctly.

◆ Prediction

Nothing in these entries suggests new functionality; expect further releases only when R or CRAN policy forces one, as this one did.

H
healthyR.data
ANALYTICS
0.0

From a bundled hospital dataset to a live CMS API client.

◆ Current state

healthyR.data supplies the data layer for the healthyverse packages. It began by shipping hospital data inside the package and now fetches from CMS and provider endpoints at call time through get_cms_meta_data(), fetch_cms_data(), and their provider counterparts. The most recent release is a single httr2 compatibility fix.

◆ Where it's heading

The 2023 release added roughly twenty current_*_data() accessors, one per CMS measure file - a wide but static surface. The 2024 releases replaced that approach with metadata lookup plus generic fetchers, then taught the fetchers to handle CSV, Excel, and ZIP payloads rather than API responses alone. The package's weight has moved from what it ships to what it can retrieve.

◆ Prediction

With the fetch layer generalised, the next visible work is more likely record-limit and error handling around httr2 than further per-measure accessors.

Alternatives to fracture and healthyR.data

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 fracture or healthyR.data.

See all fracture alternatives → · See all healthyR.data alternatives →

Recent activity from fracture and healthyR.data

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

  1. 6mo agofractureObsolete C++11 requirement removed
  2. 1y agohealthyR.datahttr2 compatibility fix
  3. 2y agohealthyR.dataFetchers handle CSV, Excel, and ZIP, with a record limit
  4. 2y agohealthyR.dataMetadata lookup and generic CMS fetchers replace bundled data
  5. 3y agohealthyR.dataTwenty CMS measure accessors added
  6. 3y agohealthyR.datacli, crayon, and rstudioapi dependencies dropped
  7. 4y agofractureNA and Inf inputs handled instead of erroring
  8. 4y agofractureExplicit denominator argument; arguments now named-only
  9. 5y agohealthyR.dataxz compression added to meet CRAN size policy
  10. 5y agofractureUnicode fraction formatting and rounding fixes

Frequently asked questions

What is the difference between fracture and healthyR.data?

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

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

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

What are the best alternatives to healthyR.data?

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