whirl
whirl turned script logging into a standardized provenance artifact regulators can read.
A side-by-side editorial comparison of b3doc and rJavaEnv — release velocity, themes, recent moves, and the top alternatives to consider.
A small B-Cubed utility for turning R Markdown into publishable docs
b3doc converts R Markdown to Markdown and rewrites front matter for documentation published by the B-Cubed project, which is its entire remit. Three releases exist: the initial pair of functions, a generalisation of the front-matter replacement, and a hardening pass that removed regex from the replace argument and standardised figures at 300 DPI. It sits in the b-cubed-eu family alongside impIndicator and shares contributors with the wider Belgian biodiversity tooling group.
The R package that installs Java for you stopped needing an update every time Java ships.
rJavaEnv downloads, caches and activates Java distributions for R projects, so packages depending on rJava can get a known runtime without system-level installation. It manages a cache, can set Java for a session only, and reports which versions are available for the detected OS and architecture. As of 0.3.0 the list of installable versions is fetched from the vendor's own release metadata rather than being hardcoded.
b3doc converts R Markdown to Markdown and rewrites front matter for documentation published by the B-Cubed project, which is its entire remit. Three releases exist: the initial pair of functions, a generalisation of the front-matter replacement, and a hardening pass that removed regex from the replace argument and standardised figures at 300 DPI. It sits in the b-cubed-eu family alongside impIndicator and shares contributors with the wider Belgian biodiversity tooling group.
The direction is toward predictability over flexibility. The replace argument arrived in 0.2.0 generalising the earlier logo-specific behaviour, then 0.3.0 pulled regex support back out of it because escape characters and over-broad matches caused unintended edits. That is a maintainer choosing a narrower tool that fails obviously over a general one that fails quietly — a reasonable trade for a package that rewrites files in place.
Expect continued small releases driven by the documentation pipeline's needs, with output-quality defaults and front-matter handling the likely subjects rather than new functions.
rJavaEnv downloads, caches and activates Java distributions for R projects, so packages depending on rJava can get a known runtime without system-level installation. It manages a cache, can set Java for a session only, and reports which versions are available for the detected OS and architecture. As of 0.3.0 the list of installable versions is fetched from the vendor's own release metadata rather than being hardcoded.
The package has been working its way out of two dependencies: on the host system and on itself. Session-scoped activation through use_java() removed the need to touch a project directory, which is what makes the package usable inside targets and callr pipelines. Dynamic version discovery then removed the maintainer from the critical path for new Java releases. What remains conspicuously thin is verification — the 0.3.0 notes put test coverage at 7.2%, an unusually candid number for a package whose job is manipulating runtime environments.
Support for Java distributions beyond Amazon Corretto is the natural next step, since the version discovery mechanism is now generic but the vendor is still singular.
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 b3doc or rJavaEnv.
whirl turned script logging into a standardized provenance artifact regulators can read.
ESPHome ships on a calendar, and the August beta train is now four builds deep.
rapr generalises its Rangeland Analysis Platform API access one endpoint at a time
An R interface to GeoPackage that keeps sanding down its own API
R's logging package handed to new maintainers and rebuilt from the inside out
Four dormant years end with a test fix, not a feature
See all b3doc alternatives → · See all rJavaEnv alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — r-package — within Infra & APIs. b3doc and rJavaEnv 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. b3doc and rJavaEnv 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 b3doc alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "b3doc alternatives" section above for the current picks, or visit /alternatives/b3doc for the full list with editorial commentary on each.
Top rJavaEnv alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "rJavaEnv alternatives" section above for the current picks, or visit /alternatives/rjavaenv for the full list with editorial commentary on each.