gpkg
An R interface to GeoPackage that keeps sanding down its own API
Comparison · Infra & APIs
discretetests vs logger
A side-by-side editorial comparison of discretetests and logger — release velocity, themes, recent moves, and the top alternatives to consider.
Shared themes:r-package
discretetests vs logger: at a glance
What is discretetests?
Four years of releases land in four minutes as the changelog gets backfilled to GitHub
DiscreteTests computes exact p-values and their full support for discrete statistical tests, returning results as a class that carries the observations, the test statistic and the null distribution. All four visible releases were tagged within four minutes of each other on a single day in May 2026, in reverse order — 0.4.1 carries the earliest timestamp and 0.4.0 the latest — so this is a historical changelog being pushed to GitHub at once, not four days of work.
What is logger?
R's logging package handed to new maintainers and rebuilt from the inside out
logger structures R logging around four composable pieces — a level threshold, a formatter, a layout and an appender — a design fixed at the 2018 CRAN release and unchanged since. The recent work is all underneath it. 0.4.0 made metadata computation lazy so expensive fields cost nothing unless a layout uses them, swapped the custom background-process appender for mirai, and added native GitHub Actions output. 0.4.1 followed with elapsed-time logging, call site location exposed to layouts, a cli-based formatter, and knitr chunk timing. 0.4.2 is a small maintenance release adding an ntfy appender.
discretetests vs logger: editorial side-by-side
discretetests
0.0INFRA · APIS
Four years of releases land in four minutes as the changelog gets backfilled to GitHub
◆ Current state
DiscreteTests computes exact p-values and their full support for discrete statistical tests, returning results as a class that carries the observations, the test statistic and the null distribution. All four visible releases were tagged within four minutes of each other on a single day in May 2026, in reverse order — 0.4.1 carries the earliest timestamp and 0.4.0 the latest — so this is a historical changelog being pushed to GitHub at once, not four days of work.
◆ Where it's heading
Read by version rather than by timestamp, the package grew from binomial, Fisher, McNemar and Poisson tests into rank-based and resampling territory: Wilcoxon signed rank and rank sum, Mann-Whitney U, a conditional homogeneity test, then sign tests and a general permutation test with several built-in statistics. Alongside that the result class was extended to hold ragged observation lists and computational detail, the print output was rewritten on cli, and the old dot-separated function names were made defunct.
◆ Prediction
The permutation test with pluggable statistics is the most open-ended addition here, and adding further built-in statistics to it is the cheapest way to extend the package from where it now stands.
logger
0.0INFRA · APIS
R's logging package handed to new maintainers and rebuilt from the inside out
◆ Current state
logger structures R logging around four composable pieces — a level threshold, a formatter, a layout and an appender — a design fixed at the 2018 CRAN release and unchanged since. The recent work is all underneath it. 0.4.0 made metadata computation lazy so expensive fields cost nothing unless a layout uses them, swapped the custom background-process appender for mirai, and added native GitHub Actions output. 0.4.1 followed with elapsed-time logging, call site location exposed to layouts, a cli-based formatter, and knitr chunk timing. 0.4.2 is a small maintenance release adding an ntfy appender.
◆ Where it's heading
Two things stand out. The original four-part architecture has absorbed six years of additions without being renegotiated — every new capability arrives as another formatter, layout or appender rather than a change to the contract. And the contributor pattern has shifted: 0.3.0 collected two years of scattered community patches, while 0.4.0 and 0.4.1 are concentrated work from a small number of prolific R-infrastructure maintainers, which reads as a handover of stewardship rather than a maintenance lull ending.
◆ Prediction
The pluggable design means new destinations and formatters are the path of least resistance, so expect further appenders in the mold of ntfy and Slack rather than changes to the core logging contract.
Alternatives to discretetests and logger
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 discretetests or logger.
portfoliobacktest
Four dormant years end with a test fix, not a feature
medicalcoder
A comorbidity-coding package relicenses to BSD and grows past the American coding systems
Dragonfly
Dragonfly spends its releases on correctness in the parts of Redis compatibility nobody tests.
Unleash
Three kill-switch explainers to one point release — Unleash's feed is content-led, not release-led.
Jackett
Jackett's daily release treadmill now spends commits undoing tracker removals it made days earlier.
See all discretetests alternatives → · See all logger alternatives →
Recent activity from discretetests and logger
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 2mo agodiscretetestsSign tests and a pluggable permutation test
- 2mo agodiscretetestsInput observation names carried through results
- 2mo agodiscretetestsWilcoxon, Mann-Whitney and homogeneity tests join the package
- 2mo agodiscretetestsmacOS compilation fix
- 3mo agologgerlogger 0.4.2 (2026-05-08)
- 11mo agologgerlogger 0.4.1 (2025-09-08)
- 11mo agologgerlogger 0.4.0 (2024-10-19)
- 11mo agologgerlogger 0.3.0 (2024-03-03)
- 11mo agologgerlogger 0.2.2 (2021-10-10)
- 11mo agologgerlogger 0.2.1 (2021-07-06)
Frequently asked questions
What is the difference between discretetests and logger?
Both compete on the same themes — r-package — within Infra & APIs. discretetests and logger 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 discretetests better than logger?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. discretetests and logger 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.
What are the best alternatives to discretetests?
Top discretetests alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "discretetests alternatives" section above for the current picks, or visit /alternatives/discretetests for the full list with editorial commentary on each.
What are the best alternatives to logger?
Top logger alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "logger alternatives" section above for the current picks, or visit /alternatives/logger for the full list with editorial commentary on each.