r2rtf
The clinical-report table engine learned Chinese, then learned to leave RTF entirely
A side-by-side editorial comparison of rtflite and spatsoc — release velocity, themes, recent moves, and the top alternatives to consider.
rtflite stopped being an RTF writer and became the conversion layer for clinical table output.
rtflite generates the RTF tables clinical study reports are built from, a Python answer to the R tooling that has owned this niche. Over one dense month it grew a full export path: DOCX in 2.2.0, DOCX concatenation in 2.3.0, a configurable LibreOffice converter in 2.4.0, and HTML plus PDF in 2.5.0. The three releases since have been documentation, test infrastructure, and typing work — the feature push has stopped and consolidation has started.
One maintainer, one or two new collective-motion metrics per release, for two years straight
spatsoc turns animal relocation data into spatial and social groupings — dyads, fission-fusion events, group centroids — and the recent history is a metronomic accretion of collective-motion measures on top of that base. Since late 2024 nearly every release has added one or two: polarization, direction to leader, position along the group axis, directional correlation delay, edge alignment, edge zones. Development is essentially single-handed; almost every merged PR in this window carries the same author.
rtflite generates the RTF tables clinical study reports are built from, a Python answer to the R tooling that has owned this niche. Over one dense month it grew a full export path: DOCX in 2.2.0, DOCX concatenation in 2.3.0, a configurable LibreOffice converter in 2.4.0, and HTML plus PDF in 2.5.0. The three releases since have been documentation, test infrastructure, and typing work — the feature push has stopped and consolidation has started.
Every format addition routes through the same LibreOffice converter rather than a per-format implementation, and 2.4.0's breaking change made that converter an injectable object you can configure and reuse. That is the shape of a package expecting to run inside a pipeline that produces hundreds of tables, not one that converts a document at a time. The recent quiet — snapshot tests moved onto `pytest-r-snapshot`, docs migrated, pandas and pyarrow dropped from dev dependencies — reads as work to stay dependency-light while the surface stabilizes.
With the export matrix filled in and three consecutive infrastructure-only releases, the next substantive change is most likely on the input side — table construction and pagination — since `page_by` and `subline_by` are the only feature area still generating bug reports in these notes.
spatsoc turns animal relocation data into spatial and social groupings — dyads, fission-fusion events, group centroids — and the recent history is a metronomic accretion of collective-motion measures on top of that base. Since late 2024 nearly every release has added one or two: polarization, direction to leader, position along the group axis, directional correlation delay, edge alignment, edge zones. Development is essentially single-handed; almost every merged PR in this window carries the same author.
The December 2025 release changes register. Alongside three new calc_distance / calc_direction / calc_centroid functions and an internal assertion family, it deprecates the `projection` argument in favour of `crs` and lands a round of checks and tests explicitly staged ahead of a new spatial interface. Read together, that is a package finishing its metric catalogue and starting to rework the coordinate-handling layer underneath it to match modern R-spatial conventions — the same evolution that made it drop its startup warning back in 0.2.7.
The next release is likely the spatial-interface rework the 0.2.12 test and assertion work was staged for, with `projection` moving from deprecated to removed. Feature additions should slow while that lands.
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 rtflite or spatsoc.
The clinical-report table engine learned Chinese, then learned to leave RTF entirely
New stewardship at openpharma, then two releases adding the methods MCP-Mod was missing
The stubbing library added httr2 support, then spent a year cutting itself free of everything else
crul took mocking back from webmockr and made it a property of the client itself
Six releases, six identical bodies — the feed carries the package abstract instead of release notes
chattr deleted every LLM integration it had written and outsourced the lot to ellmer
See all rtflite alternatives → · See all spatsoc alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. rtflite and spatsoc 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. rtflite and spatsoc 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 rtflite alternatives in Analytics are ranked by recent ship velocity. Browse the "rtflite alternatives" section above for the current picks, or visit /alternatives/rtflite for the full list with editorial commentary on each.
Top spatsoc alternatives in Analytics are ranked by recent ship velocity. Browse the "spatsoc alternatives" section above for the current picks, or visit /alternatives/spatsoc for the full list with editorial commentary on each.