tibblify
tibblify learned to derive its own specs from OpenAPI, removing the step users disliked most
A side-by-side editorial comparison of duckspatial and resmush — release velocity, themes, recent moves, and the top alternatives to consider.
duckspatial rebuilt itself around a lazy DuckDB class, then spent four releases filling in the geometry surface
duckspatial exposes DuckDB's spatial extension to R. In March 2026 it stopped being an sf convenience wrapper: 1.0.0 made duckspatial_df the primary class, a lazy table-like object that stays in DuckDB until explicitly materialized. Every function accepts and returns it by default, with mode = 'sf' as the opt-out. The four releases since have added roughly forty geometry functions on top of that foundation.
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.
duckspatial exposes DuckDB's spatial extension to R. In March 2026 it stopped being an sf convenience wrapper: 1.0.0 made duckspatial_df the primary class, a lazy table-like object that stays in DuckDB until explicitly materialized. Every function accepts and returns it by default, with mode = 'sf' as the opt-out. The four releases since have added roughly forty geometry functions on top of that foundation.
The direction is to keep work inside DuckDB and make R the orchestration layer rather than the compute layer. 1.1.0 added macros so duckspatial functions work inside dplyr verbs; 1.1.1 moved the default to DuckDB v1.5.0 native spatial storage so CRS metadata persists in GEOMETRY columns; 1.2.0 added vector-tile output via ddbs_write_mbtiles() and the full family of geometry deserializers. Feature velocity has been high and consistent since the rewrite.
The remaining gaps are in PostGIS parity — the deserializers and tile writers landed in 1.2.0, so raster support or spatial indexing are the plausible next targets. 1.2.1 being a single message-capture fix suggests the 1.2.x line is now stabilizing.
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 duckspatial 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 duckspatial 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. duckspatial 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. duckspatial 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 duckspatial alternatives in Analytics are ranked by recent ship velocity. Browse the "duckspatial alternatives" section above for the current picks, or visit /alternatives/duckspatial 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.