Nextflow
Nextflow just made AI agents a task type, alongside processes and containers.
A side-by-side editorial comparison of lares and surveytidy — release velocity, themes, recent moves, and the top alternatives to consider.
One analyst's toolbox, still shipping: Meta MMM tooling beside Wordle solvers
lares is Bernardo Lares' personal R sidekick and has never pretended otherwise — the same release adds a marketing-mix diagnostic and a function to keep your screen awake. The serious core is the Robyn/Meta arm: model selection, per-channel performance decomposition, cross-channel budget allocation. Around it sit h2o AutoML wrappers, credential and cache helpers, MP3 tagging, and a family of games.
surveytidy taught every dplyr verb to operate on a whole collection of surveys at once.
surveytidy is the tidyverse-facing half of a two-package survey stack, wrapping survey design objects from surveycore so filter, mutate, select and the rest work on them while carrying variable labels, value labels and a transformation log alongside the data. The May release extended that verb surface to survey_collection, the abstraction surveycore uses to hold several surveys as one object, so a pipeline written once dispatches across every member.
lares is Bernardo Lares' personal R sidekick and has never pretended otherwise — the same release adds a marketing-mix diagnostic and a function to keep your screen awake. The serious core is the Robyn/Meta arm: model selection, per-channel performance decomposition, cross-channel budget allocation. Around it sit h2o AutoML wrappers, credential and cache helpers, MP3 tagging, and a family of games.
Over two years the Robyn tooling matured first — robyn_performance() and robyn_modelselector() were rebuilt release after release through 2024 — and recent work has drifted outward into media and API plumbing: encrypted file helpers in 5.3.2, then an iTunes-first metadata path, MP3 tag writing, and a move of holidays() onto the Nager.Date API in 5.4.0. Cadence is roughly quarterly and the package has been quiet for three months.
The pattern in nearly every release is that a third-party API moves and lares follows it — Meta's version bumps, Robyn 3.12.0, now Nager.Date. Expect the next release to be another compatibility pass plus whatever utility the author needed that week; nothing in these entries points at a structural change.
surveytidy is the tidyverse-facing half of a two-package survey stack, wrapping survey design objects from surveycore so filter, mutate, select and the rest work on them while carrying variable labels, value labels and a transformation log alongside the data. The May release extended that verb surface to survey_collection, the abstraction surveycore uses to hold several surveys as one object, so a pipeline written once dispatches across every member.
The package is being built in two layers that arrive in order: vector-level transformations first, structural dispatch second. The make_* family in 0.4.0 handles the recoding that survey work actually consists of — labelled to factor, multi-level to dichotomous, scale reversal, valence flipping — with value labels propagating automatically. Collection support then applies data-masking, tidyselect, grouping, slicing and collapsing verbs per survey, with joins explicitly refused and a typed message reporting which surveys were skipped. Metadata fidelity is the recurring bug source: labels surviving across(), stale labels left behind by recoding, the transformation log keeping up with what the verbs did.
Joins are the one verb family that errors on collections, with users directed to join before constructing the collection, so that restriction is the clearest outstanding gap. The re-export of surveycore's collection constructors suggests the package is positioning itself as the single import users need, which points toward more re-exports as surveycore's stable API settles.
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 lares or surveytidy.
Nextflow just made AI agents a task type, alongside processes and containers.
The D-score reference implementation rebuilt its measurement foundation on seven countries.
A football-viz package just swapped scraping for an API and broke its own output to do it.
A gene-set enrichment package that outgrew its human-only origins, then went quiet.
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
See all lares alternatives → · See all surveytidy alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. lares and surveytidy 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. lares and surveytidy 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 Infra & APIs products to evaluate alongside.
Top lares alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "lares alternatives" section above for the current picks, or visit /alternatives/lares for the full list with editorial commentary on each.
Top surveytidy alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "surveytidy alternatives" section above for the current picks, or visit /alternatives/surveytidy for the full list with editorial commentary on each.