qqman
The Manhattan-plot package for GWAS results, finished and dormant since 2017.
A side-by-side editorial comparison of fossilsim and hexfont — release velocity, themes, recent moves, and the top alternatives to consider.
A fossil-record simulator that quietly grew a trait-evolution engine.
FossilSim is a mature R package for simulating fossil records on phylogenetic trees, and its release cadence reflects that: long gaps punctuated by a single capability addition. The last four releases span three years, with the most recent being a compatibility sync to its companion Shiny front-end rather than new functionality. The core simulation surface has been stable since 2022.
A GNU Unifont packager whose real work is making a huge font load fast.
hexfont ships GNU Unifont's hex bitmap files to R as bittermelon font objects, covering the full Unicode range. The last two releases were about load cost and portability: a user-level cache for precompiled fonts, then making that cache read-only by default so nothing is written unless asked. The font data itself tracks Unifont v16.0.02.
FossilSim is a mature R package for simulating fossil records on phylogenetic trees, and its release cadence reflects that: long gaps punctuated by a single capability addition. The last four releases span three years, with the most recent being a compatibility sync to its companion Shiny front-end rather than new functionality. The core simulation surface has been stable since 2022.
The arc runs from sampling mechanics toward simulating what the organisms actually were. Version 2.2.0 taught the package to handle occurrence data for occurrence birth-death models; 2.3.0 then added trait simulation under Mk, BM and OU, which is a different kind of output than fossil ages. Since then the work has been maintenance and keeping the FossilSimShiny GUI in step, suggesting the authors consider the current model set feature-complete.
The pairing of the 2.3.3 release with a FossilSimShiny version bump points to the GUI, not the library, as where the next visible work lands. The entries do not show enough activity to predict a specific new model family.
hexfont ships GNU Unifont's hex bitmap files to R as bittermelon font objects, covering the full Unicode range. The last two releases were about load cost and portability: a user-level cache for precompiled fonts, then making that cache read-only by default so nothing is written unless asked. The font data itself tracks Unifont v16.0.02.
Each release does two things — resync with a newer GNU Unifont and shave the cost of using it. The performance thread has been the more consequential one, moving from the ucp argument that restricts which code points get read, to a full precompiled cache. Version 1.0.0 also walked back the R 4.1 pipe to keep the package usable on R 4.0.
Future releases most likely follow GNU Unifont's own version cadence, with occasional cache or loading refinements.
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 fossilsim or hexfont.
The Manhattan-plot package for GWAS results, finished and dormant since 2017.
The R package for CODATA constants rebuilt its symbol table on NIST's naming so future updates stop being hand work.
The R client for AusTraits spends its releases chasing the dataset it reads.
A ggplot2 layer for seasonal adjustment output, filling in one plot type at a time.
Reference-based multiple imputation tables, shipping only what CRAN checks demand.
An MMRM tabulation package that has published nothing since its 2024 CRAN releases.
See all fossilsim alternatives → · See all hexfont alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — r-package — within Analytics. fossilsim and hexfont 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.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. fossilsim and hexfont 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 Analytics products to evaluate alongside.
Top fossilsim alternatives in Analytics are ranked by recent ship velocity. Browse the "fossilsim alternatives" section above for the current picks, or visit /alternatives/fossilsim-r for the full list with editorial commentary on each.
Top hexfont alternatives in Analytics are ranked by recent ship velocity. Browse the "hexfont alternatives" section above for the current picks, or visit /alternatives/hexfont-r for the full list with editorial commentary on each.