ESPHome
ESPHome ships on a calendar, and the August beta train is now four builds deep.
Comparison · Infra & APIs
gpkg vs portfoliobacktest
A side-by-side editorial comparison of gpkg and portfoliobacktest — release velocity, themes, recent moves, and the top alternatives to consider.
Shared themes:r-package
gpkg vs portfoliobacktest: at a glance
What is gpkg?
An R interface to GeoPackage that keeps sanding down its own API
gpkg gives R users a direct handle on GeoPackage files — the SQLite-based OGC container for vector and raster layers — through lazy table access, OGR/SQLite dialect queries and terra integration. Recent releases center on raster write ergonomics: automatic NoData selection via auto_nodata and an exported gpkg_default_nodata() following GDAL and terra conventions. Release bodies are cumulative, folding two or three versions into one entry.
What is portfoliobacktest?
Four dormant years end with a test fix, not a feature
portfolioBacktest runs portfolio strategies across multiple datasets and resampled windows, producing performance tables, leaderboards and charts. After a run of substantive releases through 2021 and early 2022 it went quiet for four years. The May 2026 release does one thing: fix unit tests against a breaking change in PerformanceAnalytics::Return.portfolio(), which now returns results for the full input series rather than only from the first weight date.
gpkg vs portfoliobacktest: editorial side-by-side
gpkg
0.0INFRA · APIS
An R interface to GeoPackage that keeps sanding down its own API
◆ Current state
gpkg gives R users a direct handle on GeoPackage files — the SQLite-based OGC container for vector and raster layers — through lazy table access, OGR/SQLite dialect queries and terra integration. Recent releases center on raster write ergonomics: automatic NoData selection via auto_nodata and an exported gpkg_default_nodata() following GDAL and terra conventions. Release bodies are cumulative, folding two or three versions into one entry.
◆ Where it's heading
The package is still finding its interface shape, and most releases pair a small capability with a deprecation or signature change — destfile giving way to y, gpkg_create_dummy_features deprecated, vapour swapped out for gdalraster. The consistent direction is deferring to GDAL and terra conventions rather than inventing gpkg-specific behaviour, and pushing connection management out of users' hands. Cadence is roughly one release a year with dependency automation now in CI.
◆ Prediction
Expect further alignment of write-path defaults with GDAL conventions and continued deprecation-with-replacement of early argument names, with an ogr2ogr-style path for out-of-memory vector data flagged as a possibility rather than a commitment.
portfoliobacktest
0.0INFRA · APIS
Four dormant years end with a test fix, not a feature
◆ Current state
portfolioBacktest runs portfolio strategies across multiple datasets and resampled windows, producing performance tables, leaderboards and charts. After a run of substantive releases through 2021 and early 2022 it went quiet for four years. The May 2026 release does one thing: fix unit tests against a breaking change in PerformanceAnalytics::Return.portfolio(), which now returns results for the full input series rather than only from the first weight date.
◆ Where it's heading
The development work is behind it. The 2019 to 2022 releases built the substance — parallel execution, resampling that works beyond stock data and beyond daily bars, transaction-cost-aware designs through w_current, and a switch from compounded to uncompounded returns in the Sharpe and annualized return calculations. Since then the package has moved only when a dependency forced it, and even then only far enough to keep the tests green.
◆ Prediction
Nothing in the entries suggests planned work; the next release is most likely triggered by another dependency change, on the same four-year-gap pattern.
Alternatives to gpkg and portfoliobacktest
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 gpkg or portfoliobacktest.
rapr
rapr generalises its Rangeland Analysis Platform API access one endpoint at a time
b3doc
A small B-Cubed utility for turning R Markdown into publishable docs
logger
R's logging package handed to new maintainers and rebuilt from the inside out
discretetests
Four years of releases land in four minutes as the changelog gets backfilled to GitHub
medicalcoder
A comorbidity-coding package relicenses to BSD and grows past the American coding systems
See all gpkg alternatives → · See all portfoliobacktest alternatives →
Recent activity from gpkg and portfoliobacktest
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 3mo agoportfoliobacktestTests fixed for a PerformanceAnalytics breaking change
- 4mo agogpkgAutomatic NoData selection for raster writes
- 1y agogpkgConnection handling reworked; table access via [ and [[
- 2y agogpkgSpatial views: dynamic layers that read as static ones
- 2y agogpkgInitial CRAN release, with OGR query support
- 4y agoportfoliobacktestSharpe ratio charts and reworked weight outputs
- 4y agoportfoliobacktestUncompounded return metrics and transaction-cost-aware designs
- 5y agoportfoliobacktestResampling generalised beyond daily stock data
- 6y agoportfoliobacktestCRAN example fixes and vignette references
- 6y agoportfoliobacktestDrawdown, cumulative return and stacked bar charts
Frequently asked questions
What is the difference between gpkg and portfoliobacktest?
Both compete on the same themes — r-package — within Infra & APIs. gpkg and portfoliobacktest 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 gpkg better than portfoliobacktest?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. gpkg and portfoliobacktest 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 gpkg?
Top gpkg alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "gpkg alternatives" section above for the current picks, or visit /alternatives/gpkg for the full list with editorial commentary on each.
What are the best alternatives to portfoliobacktest?
Top portfoliobacktest alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "portfoliobacktest alternatives" section above for the current picks, or visit /alternatives/portfoliobacktest for the full list with editorial commentary on each.