Traefik
Traefik's 2.11 line spends August fixing the names it generates for Kubernetes resources.
A side-by-side editorial comparison of dialr and JointFPM — release velocity, themes, recent moves, and the top alternatives to consider.
The R phone-number package stopped only parsing numbers and started asking them where they are.
dialr wraps Google's libphonenumber through rJava, giving R a phone vector class that parses, validates and formats international numbers. It has been quiet since August 2022, when the last release removed a pathology where Java would freeze after enough invalid inputs. The package covers parsing, validation, formatting, and the metadata lookups added in 0.3.0.
Recurrent-event modelling settles, with mean_no() promoted to stable.
JointFPM fits joint flexible parametric models for a recurrent event process alongside a competing terminal event, and predicts the mean number of events. The visible history runs from bug fixes on the earliest CRAN releases through standardization, integration options and a summary method, ending with mean_no() declared stable. Several changes arrived through outside pull requests.
dialr wraps Google's libphonenumber through rJava, giving R a phone vector class that parses, validates and formats international numbers. It has been quiet since August 2022, when the last release removed a pathology where Java would freeze after enough invalid inputs. The package covers parsing, validation, formatting, and the metadata lookups added in 0.3.0.
Two forces shape the history. One is expansion into what libphonenumber knows beyond the number itself — carrier, geocode, timezone — which happened once, in 2019, and has not been extended since. The other is the ongoing cost of being a Java wrapper inside an R tidyverse: rJava initialisation moved so the :: form works, phone vectors reclassified when tibble 3.0.0 changed how it treats list-based classes, and repeated performance work to make crossing the Java boundary tolerable. The maintainer has floated moving the phone class onto vctrs but has not.
The vctrs migration is the one change the maintainer has explicitly signalled, and the hard-deprecated one-shot functions were slated for removal in the next major release; three years of silence make neither imminent.
JointFPM fits joint flexible parametric models for a recurrent event process alongside a competing terminal event, and predicts the mean number of events. The visible history runs from bug fixes on the earliest CRAN releases through standardization, integration options and a summary method, ending with mean_no() declared stable. Several changes arrived through outside pull requests.
The arc runs from a working estimator toward a usable one: input validation and error messages first, then control over the numerical integration, then a summary method and pass-through arguments to the underlying rstpm2 fit. The latest release adds no code so much as a stability commitment to a function users were already calling.
With mean_no() stable, the next work most likely targets the prediction and standardization paths rather than the model fit itself.
Other Infra & APIs 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 dialr or JointFPM.
Traefik's 2.11 line spends August fixing the names it generates for Kubernetes resources.
nginx returns to feature work with PROXY v2 upstream writes, and quietly adds JSON to core.
ESPHome closes the 2026.8 cycle, but the release body is a bare link to the real notes.
A genomics workhorse whose visible release feed stops dead in mid-2020.
A Venn diagram package whose public release notes say almost nothing — including about its copyright cleanup.
A Shiny app for choosing the right ordinal test reached CRAN in a single 90-minute burst of tags.
See all dialr alternatives → · See all JointFPM alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. dialr and JointFPM 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.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. dialr and JointFPM 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 Infra & APIs products to evaluate alongside.
Top dialr alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "dialr alternatives" section above for the current picks, or visit /alternatives/dialr for the full list with editorial commentary on each.
Top JointFPM alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "JointFPM alternatives" section above for the current picks, or visit /alternatives/jointfpm for the full list with editorial commentary on each.