n2kanalysis
n2kanalysis has spent eight years wiring INLA models to an S3 bucket.
A side-by-side editorial comparison of broadcast and tmap — release velocity, themes, recent moves, and the top alternatives to consider.
broadcast is filling in NumPy-style array broadcasting for R, operator by operator.
broadcast brings dimension-broadcasting semantics to R arrays and lists — elementwise operations between arrays of mismatched shape, plus casting methods between hierarchical lists and dimensional structures. It reached CRAN in September 2025 and has released roughly monthly since, accumulating operators (nor, nand, longest common substring), casting methods (cast_shallow2atomic, cast_hier2dim, hiernames2dimnames), and helpers (vector2array, undim, mbroadcasters).
Two years after a from-scratch rewrite, tmap is filling in the layers v4 promised.
tmap draws thematic maps in R across static and interactive modes. The 4.0 rewrite replaced the layer syntax with explicit visual variables, scales, legends and charts, and opened the package to extensions; the 4.x line since has been steady capability fill-in. The 4.4 release adds tm_circles with fixed unit-based radii, a blend argument on every layer, and hitboxes so small objects stay clickable in view mode.
broadcast brings dimension-broadcasting semantics to R arrays and lists — elementwise operations between arrays of mismatched shape, plus casting methods between hierarchical lists and dimensional structures. It reached CRAN in September 2025 and has released roughly monthly since, accumulating operators (nor, nand, longest common substring), casting methods (cast_shallow2atomic, cast_hier2dim, hiernames2dimnames), and helpers (vector2array, undim, mbroadcasters).
The package is in its post-launch consolidation year, and the release notes read accordingly: roughly half of each entry is a consistency correction rather than an addition. Zero-length results now carry the right type, comparison operators accept integer and logical inputs, the comment attribute survives operations, and the nand operator was found to be wrongly defined against C++ short-circuit evaluation. That ratio is what a young package looks like while its edge cases are being found.
Expect more operators and casting methods on the same cadence, with continued type-consistency corrections as users exercise unusual input combinations. Nothing in the entries points at an architectural change.
tmap draws thematic maps in R across static and interactive modes. The 4.0 rewrite replaced the layer syntax with explicit visual variables, scales, legends and charts, and opened the package to extensions; the 4.x line since has been steady capability fill-in. The 4.4 release adds tm_circles with fixed unit-based radii, a blend argument on every layer, and hitboxes so small objects stay clickable in view mode.
The extension mechanism introduced in 4.0 is where the interesting work is migrating: PMTiles support arrived through a separate experimental tmap.sources package, mode cycling became configurable via tmap_mode_pool() so packages like tmap.mapgl can register themselves, and shiny dispatch methods were added specifically to let other modes integrate. The core package is increasingly a rendering contract that satellite packages plug into.
Expect more rendering backends to land as sibling packages rather than in tmap itself, with the core continuing to absorb the dispatch and mode-management plumbing they need.
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 broadcast or tmap.
n2kanalysis has spent eight years wiring INLA models to an S3 bucket.
A Fortran-descended optimizer got thread-safe, then found two flags that never worked.
ggstatsplot reached 1.0 by adding tests, having outsourced its statistics years ago.
collapse got a JSS paper and a 7x fmean speedup in the same release.
gtsummary is quietly rebuilding itself around analysis results data, one table verb at a time.
climaemet added weather alerts and wildfire risk, then spent two years managing rate limits.
See all broadcast alternatives → · See all tmap alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. broadcast and tmap 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. broadcast and tmap 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 broadcast alternatives in Analytics are ranked by recent ship velocity. Browse the "broadcast alternatives" section above for the current picks, or visit /alternatives/broadcast-r for the full list with editorial commentary on each.
Top tmap alternatives in Analytics are ranked by recent ship velocity. Browse the "tmap alternatives" section above for the current picks, or visit /alternatives/tmap-r for the full list with editorial commentary on each.