← Back to home
Comparison · Analytics

fracture vs rfm

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

fracture vs rfm: at a glance

Featurefracturerfm
SectorAnalyticsAnalytics
Velocity score0.00.0
Sparks · 30d00
Top themesnumeric formatting, fractions, utility package, maintenancer-package, customer-analytics, segmentation, dependencies
Last editorial update47m 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 rfm?

A customer segmentation package that went quiet for six years and returned with dependency hygiene

rfm computes recency, frequency and monetary segmentation for customer analytics in R. The feature surface was set early: 0.1.0 shipped a Shiny app and customer-level input, 0.2.0 added default segments and median statistics, 0.2.1 added user-specified score thresholds and returnable plot objects. Then nothing for nearly six years. Version 0.4.0 in April 2026 fixes a missing-column error and a customer id fault, and moves plotly and gganimate from Suggests to Imports.

Read the full rfm trajectory →

fracture vs rfm: 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.

R
rfm
ANALYTICS
0.0

A customer segmentation package that went quiet for six years and returned with dependency hygiene

◆ Current state

rfm computes recency, frequency and monetary segmentation for customer analytics in R. The feature surface was set early: 0.1.0 shipped a Shiny app and customer-level input, 0.2.0 added default segments and median statistics, 0.2.1 added user-specified score thresholds and returnable plot objects. Then nothing for nearly six years. Version 0.4.0 in April 2026 fixes a missing-column error and a customer id fault, and moves plotly and gganimate from Suggests to Imports.

◆ Where it's heading

The 0.4.0 release says more about maintenance posture than about product direction — the version jump past 0.3.x with only two bug fixes and a dependency reshuffle suggests a package being brought back to a releasable state rather than resuming development. Promoting plotly and gganimate to Imports makes the visualization stack mandatory, which is a heavier install in exchange for a simpler code path. The core RFM computation itself has not changed in this window.

◆ Prediction

The entries show a package returning from dormancy rather than pursuing a roadmap, so further small fixes are more likely than new segmentation capability.

Alternatives to fracture and rfm

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 rfm.

See all fracture alternatives → · See all rfm alternatives →

Recent activity from fracture and rfm

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

  1. 3mo agorfmrfm 0.4.0
  2. 6mo agofractureObsolete C++11 requirement removed
  3. 4y agofractureNA and Inf inputs handled instead of erroring
  4. 4y agofractureExplicit denominator argument; arguments now named-only
  5. 5y agofractureUnicode fraction formatting and rounding fixes
  6. 6y agorfmrfm 0.2.2
  7. 6y agorfmrfm 0.2.1
  8. 7y agorfmrfm 0.2.0
  9. 8y agorfmrfm 0.1.1
  10. 8y agorfmrfm 0.1.0

Frequently asked questions

What is the difference between fracture and rfm?

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

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

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