bittermelon
bittermelon is growing from binary bitmaps toward greyscale and color glyphs
Comparison · Analytics
mizer vs vellum
A side-by-side editorial comparison of mizer and vellum — release velocity, themes, recent moves, and the top alternatives to consider.
mizer vs vellum: at a glance
What is mizer?
After two and a half years dormant, mizer shipped three major versions in seven weeks.
The size-spectrum fish modelling package sat at 2.5.0 from December 2023 until June 2026, then released 3.0.0, 3.1.0 and 3.2.0 in the space of seven weeks. The three releases divide cleanly: 3.0.0 added biological realism through a diffusion term in the McKendrick-von Foerster equation, 3.1.0 added an opt-in second-order numerical scheme in size, and 3.2.0 rebuilt how species and resource parameters are set. Backward compatibility is handled carefully throughout — the experimental scheme is off by default and the first-order path is byte-identical to previous versions.
What is vellum?
vellum's bugs are now found by using it, not testing it — the downstream grammar is doing the QA.
The rendering engine shipped nine releases in the two weeks around the end of July, six of them on a single day. Almost every entry is a correctness fix in a capability that worked when drawn and failed when measured, or worked in isolation and failed in composition. The release notes are unusually forensic: each one states the mechanism, the observable symptom, and why the fix mirrors the draw path rather than reimplementing it.
mizer vs vellum: editorial side-by-side
mizer
5.0ANALYTICS
After two and a half years dormant, mizer shipped three major versions in seven weeks.
◆ Current state
The size-spectrum fish modelling package sat at 2.5.0 from December 2023 until June 2026, then released 3.0.0, 3.1.0 and 3.2.0 in the space of seven weeks. The three releases divide cleanly: 3.0.0 added biological realism through a diffusion term in the McKendrick-von Foerster equation, 3.1.0 added an opt-in second-order numerical scheme in size, and 3.2.0 rebuilt how species and resource parameters are set. Backward compatibility is handled carefully throughout — the experimental scheme is off by default and the first-order path is byte-identical to previous versions.
◆ Where it's heading
Two threads run through the 3.x line. The first is numerical: diffusion, then higher-order accuracy in both size and time, with explicit warnings that enabling them shifts diagnostics and may require recalibration. The second is making the package composable — extensions now work regardless of load order, and parameter assignment propagates to the derived rate arrays instead of being silently discarded. That second thread reads as the more consequential one: the 3.2.0 notes describe scalar edits that previously vanished and now accumulate, which is the kind of fix that changes what published model configurations actually computed.
◆ Prediction
Expect the experimental second-order scheme to move toward default-on once recalibration guidance exists, and the patch line to keep absorbing the documentation and website gaps that 3.2.1 started on.
vellum
5.0ANALYTICS
vellum's bugs are now found by using it, not testing it — the downstream grammar is doing the QA.
◆ Current state
The rendering engine shipped nine releases in the two weeks around the end of July, six of them on a single day. Almost every entry is a correctness fix in a capability that worked when drawn and failed when measured, or worked in isolation and failed in composition. The release notes are unusually forensic: each one states the mechanism, the observable symptom, and why the fix mirrors the draw path rather than reimplementing it.
◆ Where it's heading
The pivotal detail is stated outright in 0.6.3 — the first bug in the series found by using the engine from vellumplot rather than testing it in isolation. Every release since names the downstream as the source: the contrast rule's false positives, the lint rules that fired on all five sample plots, the keyed roundrect batch. A rendering engine with a real grammar built on top of it is now getting the integration coverage that unit tests structurally cannot provide, and the fixes are converging on one theme: the measurement path and the draw path must not drift.
◆ Prediction
Expect the release rate to fall as the vellumplot integration surface is exhausted, with remaining work concentrated in the lint rule set now that it is meant to gate builds rather than just inform.
Alternatives to mizer and vellum
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 mizer or vellum.
epiworldR
epiworldR is a thin R shell whose releases track the C++ simulator underneath it
watina
A groundwater database client that has started doing the domain analysis too
inbospatial
A thin R wrapper over Flemish geospatial services, adding one standard at a time
Fluent Bit
Fluent Bit keeps two lines alive while the 5.x branch quietly opens 5.1.
OpenCTI
OpenCTI is rebuilding its connector layer into a marketplace and wiring the platform to XTM Hub
See all mizer alternatives → · See all vellum alternatives →
Recent activity from mizer and vellum
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 11d agovellumLinter grows to 20 rules and stops firing on every plot
- 13d agovellumAnimated SVGs no longer blink once and vanish or play in reverse
- 13d agovellumPick table now reports device pixels instead of two coordinate systems
- 14d agovellumContrast rule stops flagging every plot; gridlines become PDF artifacts
- 14d agovellumgrobwidth and grobheight now measure wrapped text, not the unwrapped line
- 15d agovellumKeyed roundrect becomes a real batch after downstream integration exposes it
- 15d agomizerpkgdown index fix for a man page added after the 3.2.0 build
- 25d agomizerParameter assignment rebuilds derived rates; extensions compose in any load order
- 1mo agomizerOpt-in second-order accurate scheme in the size variable
- 2mo agomizerDiffusion enters the McKendrick-von Foerster equation, ending a two-year gap ⚡
- 2y agomizerExternal encounter rate, and a split between given and calculated parameters
- 3y agomizerw_inf renamed to w_max to separate maximum size from von Bertalanffy asymptotic size
Frequently asked questions
What is the difference between mizer and vellum?
They serve adjacent needs but don't currently overlap on shipped themes. mizer and vellum are shipping at a similar cadence (velocity 5.0 vs 5.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 mizer better than vellum?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. mizer and vellum are shipping at a similar cadence (velocity 5.0 vs 5.0, both within Sparkpulse's "active" band). For your specific use case, the alternatives sections above list other Analytics products to evaluate alongside.
What are the best alternatives to mizer?
Top mizer alternatives in Analytics are ranked by recent ship velocity. Browse the "mizer alternatives" section above for the current picks, or visit /alternatives/mizer-r for the full list with editorial commentary on each.
What are the best alternatives to vellum?
Top vellum alternatives in Analytics are ranked by recent ship velocity. Browse the "vellum alternatives" section above for the current picks, or visit /alternatives/vellum-r for the full list with editorial commentary on each.