← Back to home
Comparison · Infra & APIs

Luminescence vs q2

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

Luminescence vs q2: at a glance

FeatureLuminescenceq2
SectorInfra & APIsInfra & APIs
Velocity score2.56.3
Sparks · 30d01
Top themesr-package, luminescence-dating, geochronology, dose-responserust-rewrite, publishing-toolchain, quarto, theming
Last editorial update21h ago9h ago
WebsiteVisit →Visit →

What is Luminescence?

Luminescence is revisiting the statistical assumptions baked into its dose-response fits.

The package provides luminescence dating analysis for the geochronology community — signal import from several instrument formats, dose-response curve fitting, and a large library of analysis routines. The current release changes how fitting weights are handled by default, on the reasoning that individual relative uncertainties do not in fact scale with dose as the previous approach assumed. Several releases in this window are historical versions backfilled into the feed, so their timestamps sit within minutes of each other and do not reflect when the work shipped.

Read the full Luminescence trajectory →

What is q2?

After two releases pulling ahead, q2 spends v0.23.0 back on parity: light/dark theming.

q2 is the Quarto team's Rust reimplementation of the publishing toolchain, shipping as a statically linked single binary with minisign-signed archives and a bundled Quarto Hub MCP server, still marked experimental and not production-ready. The cadence holds at roughly a release a day through mid-August, with raw commit logs standing in for curated notes. v0.22.0 was the break in the pattern — llms.txt site output and a live-share preview, the first capability the original toolchain does not have. v0.23.0 goes straight back to closing the parity gap, and does it at epic scale.

Read the full q2 trajectory →

Luminescence vs q2: editorial side-by-side

L
Luminescence
INFRA · APIS
2.5

Luminescence is revisiting the statistical assumptions baked into its dose-response fits.

◆ Current state

The package provides luminescence dating analysis for the geochronology community — signal import from several instrument formats, dose-response curve fitting, and a large library of analysis routines. The current release changes how fitting weights are handled by default, on the reasoning that individual relative uncertainties do not in fact scale with dose as the previous approach assumed. Several releases in this window are historical versions backfilled into the feed, so their timestamps sit within minutes of each other and do not reflect when the work shipped.

◆ Where it's heading

Two kinds of change dominate. The first is deliberate breaking changes made for correctness or consistency: the weighting rework, and import functions now uniformly appending the detector to record types so all formats behave as one always did. The second is a steady stream of new analysis functions contributed by the wider research community, covering crosstalk correction, spatial autocorrelation on grain discs, and incomplete bleaching models. Deprecated functions are being removed on a clear schedule rather than left indefinitely.

◆ Prediction

Expect further consolidation of defaults that were inherited rather than chosen, since the weighting change is framed as correcting earlier reasoning rather than adding an option.

Q
q2
INFRA · APIS
6.3

After two releases pulling ahead, q2 spends v0.23.0 back on parity: light/dark theming.

◆ Current state

q2 is the Quarto team's Rust reimplementation of the publishing toolchain, shipping as a statically linked single binary with minisign-signed archives and a bundled Quarto Hub MCP server, still marked experimental and not production-ready. The cadence holds at roughly a release a day through mid-August, with raw commit logs standing in for curated notes. v0.22.0 was the break in the pattern — llms.txt site output and a live-share preview, the first capability the original toolchain does not have. v0.23.0 goes straight back to closing the parity gap, and does it at epic scale.

◆ Where it's heading

The light-dark epic is the shape of how this team retires a Quarto 1 feature: a design doc, then ThemeConfig growing a parsed dark variant, dual theme compilation with color-scheme emission, attributed stylesheet links, a color-mode toggle runtime, an accessibility-aware highlight-style reader, a brand light/dark seam, and an end-to-end verification pass against quarto-web before the docs land. One phase (D) was deferred with its options recorded rather than dropped. Around it, panel-tabset support lands, format.html.css is finally copied and rebased per page, and the llms companion output gains a link-format attribute so authors control where companion links point — the one thread tying this release back to the v0.22.0 work.

◆ Prediction

Expect the remaining Q1 parity items to keep setting the release agenda, with the deferred light-dark phase D and the freshly opened panel-tabset plan the two named strands most likely to fill the next few tags. npx distribution for the standalone Quarto Hub MCP bundle is still the only distribution item the notes explicitly call planned.

Alternatives to Luminescence and q2

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 Luminescence or q2.

See all Luminescence alternatives → · See all q2 alternatives →

Recent activity from Luminescence and q2

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

  1. 1d agoq2Light/dark themes with a color-mode toggle; panel-tabset support
  2. 4d agoq2llms.txt site output and a live-share collaborative preview
  3. 5d agoq2TOC entries carry inline markup; draft banner restored
  4. 6d agoq2Adds alias redirect stubs and diagnostic suppression
  5. 6d agoq2Bumps samod and automerge; fixes indented continuations
  6. 7d agoq2Lua filters supported; mermaid bundled instead of CDN-loaded
  7. 26d agoLuminescenceReworks dose-response fitting weights, changing prior defaults
  8. 4mo agoLuminescenceFixes an uninitialised array and background overcounting
  9. 5mo agoLuminescenceImport functions now append detector type to record names
  10. 7mo agoLuminescenceAdds crosstalk correction, Moran's I, and dose-response fitting
  11. 7mo agoLuminescenceFixes baSAR reporting, fading input checks, and plot regressions
  12. 7mo agoLuminescenceAdds automatic background subtraction and record removal helpers

Frequently asked questions

What is the difference between Luminescence and q2?

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

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. q2 is currently shipping more aggressively (velocity 6.3 vs 2.5), with 1 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other Infra & APIs products to evaluate alongside.

What are the best alternatives to Luminescence?

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

What are the best alternatives to q2?

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