tibblify
tibblify learned to derive its own specs from OpenAPI, removing the step users disliked most
A side-by-side editorial comparison of parglm and resmush — release velocity, themes, recent moves, and the top alternatives to consider.
Under a new maintainer, parglm traded raw speed work for glm parity and memory safety
parglm fits generalized linear models using parallel QR decomposition, targeting datasets where glm() is too slow. Tom Palmer took over maintenance at 0.1.8 in April 2026, and the package has released five times since — a burst of activity after a long quiet period. 0.2.0 in July 2026 is the first release to focus on correctness rather than throughput.
resmush declared itself finished and has shipped nothing but maintenance since.
resmush compresses images through the reSmush.it API from R. Version 1.0.0 was an explicit maturity statement rather than a feature release: the major version was bumped to signal a stable development state, the minimum R version moved to 4.1.0, and documentation moved to Quarto. The two releases since are console message polish, an internals refactor, and mock-based tests.
parglm fits generalized linear models using parallel QR decomposition, targeting datasets where glm() is too slow. Tom Palmer took over maintenance at 0.1.8 in April 2026, and the package has released five times since — a burst of activity after a long quiet period. 0.2.0 in July 2026 is the first release to focus on correctness rather than throughput.
The arc runs from performance to trustworthiness. 0.1.9 was a large optimization release — deque-based task queues, fused memory passes, upper-triangle-only Fisher information, thread_local IDs — plus ecosystem integration with sandwich and gtsummary. 0.2.0 then fixed an out-of-bounds write triggered by small block_size values and a path where a non-finite working response could poison the QR decomposition, and brought response-type handling in line with glm().
With the memory-safety issues addressed and glm parity closed for binomial responses, further work is likely to extend family coverage or the benchmark suite rather than revisit the threading model. The C++17 requirement set at 0.1.8 gives room for more aggressive optimization if the maintainer returns to that.
resmush compresses images through the reSmush.it API from R. Version 1.0.0 was an explicit maturity statement rather than a feature release: the major version was bumped to signal a stable development state, the minimum R version moved to 4.1.0, and documentation moved to Quarto. The two releases since are console message polish, an internals refactor, and mock-based tests.
This is a package in maintenance by design. The functional surface has not changed since 0.2.2 added a dry-run check and a referer header to the API calls, and the notable earlier change was subtractive, dropping webp when the upstream API stopped accepting it. Recent activity is dominated by dependency bumps and testing work, with mocks replacing live API calls in the test suite.
Expect the same maintenance cadence, with the most likely source of a real change being another format or endpoint shift at the reSmush.it API rather than anything originating in the package.
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 parglm or resmush.
tibblify learned to derive its own specs from OpenAPI, removing the step users disliked most
spsurvey has spent four years consolidating after its 5.0.0 rewrite rather than adding to it
StreamCatTools is quietly moving off web services and onto cloud-native GeoParquet
reproducible added a windowed read path so remote GeoTiffs never fully download
qcTAF is building an automated checklist for reproducible fisheries assessments, one criterion at a time
After three dormant years, rpymat returned to fix the OpenMP crash that breaks R and conda together
See all parglm alternatives → · See all resmush alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. parglm and resmush 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. parglm and resmush 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 parglm alternatives in Analytics are ranked by recent ship velocity. Browse the "parglm alternatives" section above for the current picks, or visit /alternatives/parglm for the full list with editorial commentary on each.
Top resmush alternatives in Analytics are ranked by recent ship velocity. Browse the "resmush alternatives" section above for the current picks, or visit /alternatives/resmush for the full list with editorial commentary on each.