rphylopic
The R package that puts organism silhouettes on plots keeps widening where they can be drawn.
Comparison · Analytics
fluxnet-package vs lstar
A side-by-side editorial comparison of fluxnet-package and lstar — release velocity, themes, recent moves, and the top alternatives to consider.
fluxnet-package vs lstar: at a glance
What is fluxnet-package?
fluxnet keeps swapping its own plumbing — first a Python downloader, now a DuckDB backend.
fluxnet gives R users access to FLUXNET eddy covariance data: listing sites, downloading, quality control and citation. Two releases in three months replaced the parts underneath the user-facing functions — 0.3.0 moved downloading off httr2 onto the fluxnet_shuttle Python library, and 0.6.0 added experimental DuckDB ingest so data can be queried with dplyr without being read into memory. The API around them has been churning in step, with site_ids='all' deprecated and max_gapfill renamed to threshold.
What is lstar?
A single-cell data store commits to Zarr v3 and range-readable hosting across four language surfaces
lstar stores single-cell data behind one C++ core with Python, R and JS/WASM bindings, and ships a browser viewer that reads the store directly. Zarr v3 is now the default on-disk format across all four surfaces, with zstd compression and sharding that packs many chunks into fewer objects. Viewer stores are compressed per field and resolved at chunk granularity, so a hosted viewer fetches only what it displays. The tag stream carries both lstar and lstar-sc releases.
fluxnet-package vs lstar: editorial side-by-side
fluxnet-package
0.0ANALYTICS
fluxnet keeps swapping its own plumbing — first a Python downloader, now a DuckDB backend.
◆ Current state
fluxnet gives R users access to FLUXNET eddy covariance data: listing sites, downloading, quality control and citation. Two releases in three months replaced the parts underneath the user-facing functions — 0.3.0 moved downloading off httr2 onto the fluxnet_shuttle Python library, and 0.6.0 added experimental DuckDB ingest so data can be queried with dplyr without being read into memory. The API around them has been churning in step, with site_ids='all' deprecated and max_gapfill renamed to threshold.
◆ Where it's heading
The direction is toward handling data volumes that do not fit the read-it-all-into-R model, and toward borrowing rather than reimplementing — a Python library for transfers, DuckDB for storage. That comes with dependency weight the package now has to manage itself, which is what flux_install_shuttle() and its virtualenv handling exist for. Renames and deprecations in nearly every release suggest the interface is being fixed as the backend settles rather than the other way around.
◆ Prediction
The DuckDB functions are marked experimental and cover connect, build and update only, so the next step is most likely stabilising them and routing the existing quality-control and extraction functions through the database rather than around it.
lstar
5.0ANALYTICS
A single-cell data store commits to Zarr v3 and range-readable hosting across four language surfaces
◆ Current state
lstar stores single-cell data behind one C++ core with Python, R and JS/WASM bindings, and ships a browser viewer that reads the store directly. Zarr v3 is now the default on-disk format across all four surfaces, with zstd compression and sharding that packs many chunks into fewer objects. Viewer stores are compressed per field and resolved at chunk granularity, so a hosted viewer fetches only what it displays. The tag stream carries both lstar and lstar-sc releases.
◆ Where it's heading
The through-line is making a hosted store cheap to read. Sharding addresses the file-per-chunk explosion that makes many-chunk arrays awkward to host; per-field compression with chunk-granular resolution means colouring an embedding by one gene fetches one column rather than an array. The 0.2.x patches are the cost of maintaining four surfaces at once — a WASM heap crash that only browsers exercise, and a count-basis orientation defect where all three surfaces normalized in memory and none owned the on-disk layout.
◆ Prediction
The orientation bug's root cause — no surface owning the on-disk representation while all three normalized in memory — is the kind of gap that usually produces a validation or ownership change rather than another point fix.
Alternatives to fluxnet-package and lstar
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 fluxnet-package or lstar.
bbk
One R interface is absorbing the world's central bank data portals, one API at a time.
treasury
A thin Treasury rates wrapper has stopped adding endpoints and started making its tables self-describing.
soilDB
The R front door to USDA soil data finishes a long deprecation cleanup and turns local-first.
quanteda
Text analysis in R keeps optimising its token internals — and builds a path out to torch
moderndive
The ModernDive teaching package learns to render inside the browser that runs its own textbook
See all fluxnet-package alternatives → · See all lstar alternatives →
Recent activity from fluxnet-package and lstar
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 21d agolstarViewer count-basis orientation fixed; existing stores need re-prep
- 26d agolstarWASM viewer crash on resizable heaps fixed
- 1mo agolstarlstar 0.2.0 ⚡
- 1mo agolstarMeasure state inferred from content, not slot name
- 1mo agofluxnet-packageExperimental DuckDB backend for out-of-memory queries ⚡
- 1mo agofluxnet-packageflux_qc() handles hourly data; max_gapfill renamed to threshold
- 2mo agofluxnet-packageflux_citations() for site-level citation output
- 3mo agofluxnet-packageFix for multiple site_ids regression
- 3mo agofluxnet-packagesite_ids='all' deprecated in favour of NULL
- 3mo agofluxnet-packageDownloads move to the fluxnet_shuttle Python library ⚡
Frequently asked questions
What is the difference between fluxnet-package and lstar?
They serve adjacent needs but don't currently overlap on shipped themes. lstar is currently shipping more aggressively (velocity 5.0 vs 0.0), with 0 editorial sparks in the last 30 days against 0. See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.
Is fluxnet-package better than lstar?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. lstar is currently shipping more aggressively (velocity 5.0 vs 0.0), with 0 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other Analytics products to evaluate alongside.
What are the best alternatives to fluxnet-package?
Top fluxnet-package alternatives in Analytics are ranked by recent ship velocity. Browse the "fluxnet-package alternatives" section above for the current picks, or visit /alternatives/fluxnet-package for the full list with editorial commentary on each.
What are the best alternatives to lstar?
Top lstar alternatives in Analytics are ranked by recent ship velocity. Browse the "lstar alternatives" section above for the current picks, or visit /alternatives/lstar for the full list with editorial commentary on each.