TidyDensity
A distribution catalogue that grows by one family at a time, and rarely breaks anything.
A side-by-side editorial comparison of churon and sd2r — release velocity, themes, recent moves, and the top alternatives to consider.
churon is spending its entire release history getting a Rust ONNX binding through CRAN.
An R package wrapping ONNX Runtime through Rust. All three releases in the window land within four days and none of them adds a feature. 0.1.8 downgrades the ort crate to 2.0.0-rc.10 because rc.11 needs Rust Edition 2024 and CRAN's Windows machines run Rust 1.81. 0.1.10 removes the vendored Rust sources from git into a compressed tarball for offline builds, fixes the Windows extraction path, deletes dead Rust and R code, and bumps ONNX Runtime to 1.23.2.
Local Stable Diffusion inference lands in R, shipped as Rcpp bindings over stable-diffusion.cpp
sd2r is a young project wrapping stable-diffusion.cpp for R via Rcpp. The 0.1.0 release established the package structure and the core call surface — sd_ctx(), sd_txt2img(), sd_save_image() — with Vulkan GPU support behind a configure flag and a worked SD 1.5 example at 512x512. The two releases since are not code but asset bundles: precompiled tokenizer vocabularies and BPE merge tables shipped as header files, growing from four tokenizers to twelve.
An R package wrapping ONNX Runtime through Rust. All three releases in the window land within four days and none of them adds a feature. 0.1.8 downgrades the ort crate to 2.0.0-rc.10 because rc.11 needs Rust Edition 2024 and CRAN's Windows machines run Rust 1.81. 0.1.10 removes the vendored Rust sources from git into a compressed tarball for offline builds, fixes the Windows extraction path, deletes dead Rust and R code, and bumps ONNX Runtime to 1.23.2.
Every visible decision is set by CRAN's build environment rather than by the package's own roadmap — pinned to an older ort release, vendored dependencies restructured for offline builds, and a dedicated CI job that simulates CRAN without network access. That is the standing cost of shipping a Rust-backed inference binding through R's distribution channel, and it is consuming the release stream entirely.
Expect the ort pin to move forward only when CRAN's Windows toolchain reaches a newer Rust, since that constraint is stated explicitly as the reason for the downgrade.
sd2r is a young project wrapping stable-diffusion.cpp for R via Rcpp. The 0.1.0 release established the package structure and the core call surface — sd_ctx(), sd_txt2img(), sd_save_image() — with Vulkan GPU support behind a configure flag and a worked SD 1.5 example at 512x512. The two releases since are not code but asset bundles: precompiled tokenizer vocabularies and BPE merge tables shipped as header files, growing from four tokenizers to twelve.
The asset releases are the more revealing half of this history. The first bundle covered CLIP, Mistral, Qwen and UMT5 — enough for SD 1.x through Flux. The second adds T5, Gemma, Gemma2 and GPT-OSS merges and splits UMT5 out as the Wan video encoder, so the tokenizer surface now reaches well beyond the image models the package currently exposes. Vocabulary support is being staged ahead of the inference paths that would use it.
Given that tokenizers for Flux, SD3 and the Wan video encoder are already bundled while the documented API stops at txt2img, the next step is most likely exposing those model families through the R interface.
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 churon or sd2r.
A distribution catalogue that grows by one family at a time, and rarely breaks anything.
College football's open data client hit v2 — and now reports how many API calls you have left.
The USA phenology data client rebuilt its entire stack and stopped handing users -9999 as a number.
GeneNMF rebuilt how it derives meta-programs, changing every result it had produced.
Publication-ready psychology tables and plots, tracking APA style as closely as the software allows.
A spatial-statistics utility package exists to be depended on, and is built accordingly.
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. churon and sd2r 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. churon and sd2r 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.
Top churon alternatives in Analytics are ranked by recent ship velocity. Browse the "churon alternatives" section above for the current picks, or visit /alternatives/churon for the full list with editorial commentary on each.
Top sd2r alternatives in Analytics are ranked by recent ship velocity. Browse the "sd2r alternatives" section above for the current picks, or visit /alternatives/sd2r for the full list with editorial commentary on each.