← Back to home
Comparison · Analytics

lstar vs moderndive

A side-by-side editorial comparison of lstar and moderndive — release velocity, themes, recent moves, and the top alternatives to consider.

lstar vs moderndive: at a glance

Featurelstarmoderndive
SectorAnalyticsAnalytics
Velocity score5.02.5
Sparks · 30d00
Top themessingle-cell-genomics, zarr, wasm, data-formatsstatistics-education, webr, regression, r-package
Last editorial update1h ago1h ago
WebsiteVisit →Visit →

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.

Read the full lstar trajectory →

What is moderndive?

The ModernDive teaching package learns to render inside the browser that runs its own textbook

moderndive supplies the datasets, regression helpers and ggplot geoms used by the ModernDive introductory statistics textbook. Its release history is mostly dataset accumulation — much of it contributed by students in batches — punctuated by occasional function work. The latest release is different: it fixes View() so it renders inside webR, the in-browser R that powers the book's live exercises, and reworks the regression helpers to survive in-formula transformations.

Read the full moderndive trajectory →

lstar vs moderndive: editorial side-by-side

L
lstar
ANALYTICS
5.0

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.

M
moderndive
ANALYTICS
2.5

The ModernDive teaching package learns to render inside the browser that runs its own textbook

◆ Current state

moderndive supplies the datasets, regression helpers and ggplot geoms used by the ModernDive introductory statistics textbook. Its release history is mostly dataset accumulation — much of it contributed by students in batches — punctuated by occasional function work. The latest release is different: it fixes View() so it renders inside webR, the in-browser R that powers the book's live exercises, and reworks the regression helpers to survive in-formula transformations.

◆ Where it's heading

The package is following the textbook's second edition into the browser. webR has no pandoc, so the DT htmlwidget path the package relied on cannot produce the self-contained HTML the notebook cell needs, and the auto-print path was gated behind interactive() being false — meaning students working through the live exercises saw an explanatory message where a table should have been. Building a static HTML table and pushing it through webR's viewer hook is a small change with a direct effect on whether the book's interactive mode works at all.

◆ Prediction

With the book's v2 datasets landed and the browser rendering path fixed, the remaining friction is most likely in other functions that assume a desktop R session.

Alternatives to lstar and moderndive

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 lstar or moderndive.

See all lstar alternatives → · See all moderndive alternatives →

Recent activity from lstar and moderndive

Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.

  1. 12d agomoderndiveView() renders in webR; regression helpers survive formula transforms
  2. 21d agolstarViewer count-basis orientation fixed; existing stores need re-prep
  3. 26d agolstarWASM viewer crash on resizable heaps fixed
  4. 1mo agolstarlstar 0.2.0
  5. 1mo agolstarMeasure state inferred from content, not slot name
  6. 1y agomoderndiveDatasets and tidy_summary() for the second edition
  7. 2y agomoderndiveAlmond and flight datasets for the inference chapters
  8. 4y agomoderndiveTen student-curated teaching datasets
  9. 4y agomoderndiveAlaska flights subset added
  10. 5y agomoderndiveCleaner regression tables and an explicit conf.level argument

Frequently asked questions

What is the difference between lstar and moderndive?

They serve adjacent needs but don't currently overlap on shipped themes. lstar is currently shipping more aggressively (velocity 5.0 vs 2.5), 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 lstar better than moderndive?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. lstar is currently shipping more aggressively (velocity 5.0 vs 2.5), 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 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.

What are the best alternatives to moderndive?

Top moderndive alternatives in Analytics are ranked by recent ship velocity. Browse the "moderndive alternatives" section above for the current picks, or visit /alternatives/moderndive for the full list with editorial commentary on each.