rollupTree
The recursive-computation engine under massProps grows the accessors its consumer needed
A side-by-side editorial comparison of tabular and valr — release velocity, themes, recent moves, and the top alternatives to consider.
tabular went from clinical tables to complete TFL output in under two months.
tabular renders pre-summarised clinical tables, figures and listings to RTF, LaTeX, HTML, PDF, DOCX, Markdown and now Typst from one immutable verb pipeline, with no external SAS or Java runtime. It arrived in June 2026 as a CRAN submission candidate, added figure() a month later to cover the F in TFL, and has spent the 0.3.x line on speed, font resolution and toolchain diagnostics.
valr's interval verbs now read genomic files in place instead of demanding a loaded tibble.
valr reimplements bedtools-style genome interval arithmetic as tidyverse verbs backed by C++. Its long project has been closing the behavioural gap with bedtools — the book-ended interval semantics finally match in 0.10.0, three releases after the deprecation began. The July release also ends the assumption that intervals must be in memory: bed_map(), bed_intersect(), bed_subtract(), bed_coverage() and bed_window() accept a bigWig or bigBed path or URL where an interval table used to go.
tabular renders pre-summarised clinical tables, figures and listings to RTF, LaTeX, HTML, PDF, DOCX, Markdown and now Typst from one immutable verb pipeline, with no external SAS or Java runtime. It arrived in June 2026 as a CRAN submission candidate, added figure() a month later to cover the F in TFL, and has spent the 0.3.x line on speed, font resolution and toolchain diagnostics.
The work is converging on backend parity — one spec should render the same wherever you emit it. Recent notes are almost entirely gap-closing between targets: bold column headers and page-width correction on LaTeX, cell margins on DOCX, group-separator blank rows re-expressed as discardable space so a page never ends on a stray gap, whitespace collapsing honoured on Typst. Diagnostics are keeping pace, with check_latex() probing through kpsewhich and check_typst() auditing the compiler and font chain.
With both toolchain checkers in place, the friction that remains is environmental rather than featural, and the notes point to further parity and packaging fixes rather than another backend. Whether Typst becomes the default PDF path instead of LaTeX is not something these notes settle.
valr reimplements bedtools-style genome interval arithmetic as tidyverse verbs backed by C++. Its long project has been closing the behavioural gap with bedtools — the book-ended interval semantics finally match in 0.10.0, three releases after the deprecation began. The July release also ends the assumption that intervals must be in memory: bed_map(), bed_intersect(), bed_subtract(), bed_coverage() and bed_window() accept a bigWig or bigBed path or URL where an interval table used to go.
Two arcs converge here. One is compatibility: min_overlap arrived with a deprecation warning in 0.9.0 and its default flipped from 0 to 1 in 0.10.0, so book-ended intervals are excluded by default as bedtools does, with the internal calculations in bed_closest() and friends deliberately left counting them. The other is the file-backed path, which grew out of the cpp11bigwig dependency adopted in 0.8.3 for read_bigwig() and re-exported in 0.9.0 — reading a file became querying one. Underneath, the C++ base keeps getting lighter: Rcpp swapped for cpp11, rlang cut to a single function, per-group memory copies removed from three verbs.
Only five verbs take a file argument today and bed_closest(), bed_glyph() and the statistical verbs do not, so extending the file-backed path across the rest of the API is the obvious follow-up. The deprecated tibble re-exports and the now-defunct n_fields argument suggest continued removal of the compatibility layer in the next minor release.
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 tabular or valr.
The recursive-computation engine under massProps grows the accessors its consumer needed
A mass-properties rollup spends a year on documentation and follows its sibling's API
Six months of releases and not one of them touched the scoring models
A cognitive-science sampling package ships once, then goes quiet for eighteen months
A Bayesian volatility sampler in its maintenance decade, paying for its own speed
A black-box interpreter reaches CRAN, then learns multi-class and survival responses
See all tabular alternatives → · See all valr alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — r-packages — within Infra & APIs. tabular is currently shipping more aggressively (velocity 2.5 vs 0.0), 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.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. tabular is currently shipping more aggressively (velocity 2.5 vs 0.0), with 0 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.
Top tabular alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "tabular alternatives" section above for the current picks, or visit /alternatives/tabular for the full list with editorial commentary on each.
Top valr alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "valr alternatives" section above for the current picks, or visit /alternatives/valr for the full list with editorial commentary on each.