ggpointless
ggpointless keeps adding the ggplot2 layers nobody else bothered to write.
A side-by-side editorial comparison of artoo and surveycore — release velocity, themes, recent moves, and the top alternatives to consider.
artoo makes any-to-any clinical dataset conversion lossless by construction.
artoo reads and writes SAS XPORT, CDISC Dataset-JSON, NDJSON, Parquet and RDS around one canonical metadata model, so a conversion between any two formats carries labels, CDISC types, lengths, display formats, controlled-terminology references and sort keys intact. It is pure R with no SAS or Java runtime. It reached CRAN at 0.1.1 and has spent 0.1.2 and 0.1.3 on the character-encoding edges.
surveycore declared its API stable with every survey design type covered.
surveycore is the estimation engine of a two-package survey stack, handling design objects and variance estimation while surveytidy supplies the dplyr verbs on top. The June release marks it 1.0.0 and states the API is complete and stable across Taylor series linearization, replicate weights, two-phase and non-probability designs, with means, totals, frequencies, quantiles, ratios, correlations, regression, t-tests, ANOVA and effective sample size all in place.
artoo reads and writes SAS XPORT, CDISC Dataset-JSON, NDJSON, Parquet and RDS around one canonical metadata model, so a conversion between any two formats carries labels, CDISC types, lengths, display formats, controlled-terminology references and sort keys intact. It is pure R with no SAS or Java runtime. It reached CRAN at 0.1.1 and has spent 0.1.2 and 0.1.3 on the character-encoding edges.
Recent work is all about text that does not survive a format change. 0.1.3 adds an invalid_encoding dimension to artoo_checks() that flags bytes which are not valid UTF-8 before a writer aborts on them, accepts the SAS OEM/DOS encoding names, and gives the writers on_invalid = "translit" and "fold" so smart punctuation and accented characters resolve to pinned ASCII instead of failing. The fold tables ship as data specifically so the result is identical on every platform, which is the same determinism argument behind C-locale row sorting in 0.1.0.
The new WLATIN1-to-UTF-8 migration article and the width warning on write_xpt() point the next attention at length and truncation semantics rather than at additional formats. These notes name no further target format.
surveycore is the estimation engine of a two-package survey stack, handling design objects and variance estimation while surveytidy supplies the dplyr verbs on top. The June release marks it 1.0.0 and states the API is complete and stable across Taylor series linearization, replicate weights, two-phase and non-probability designs, with means, totals, frequencies, quantiles, ratios, correlations, regression, t-tests, ANOVA and effective sample size all in place.
The last months before 1.0.0 were spent making the awkward designs behave like the ordinary ones. Non-probability designs gained jackknife replicate schemes and got their bootstrap repweights routed through the replicate-weight variance estimator in survey_glm(), matching every other estimation function. The survey_collection abstraction — several surveys treated as one pseudo-data-frame — was tightened rather than extended: divergent grouping across members now errors instead of stitching a patchwork with bind_rows(), and the missing-variable argument was renamed and given a stored default on the collection itself. A documentation audit before 1.0.0 turned up six dispatch and print bugs and corrections across forty-plus files, which is the kind of thing that surfaces when an API is being frozen rather than extended.
A declared-stable API means the next releases should be additive or corrective rather than breaking, and the pre-1.0.0 pattern of breaking renames should stop. The tight version pinning between the two packages means surveytidy releases will keep following surveycore's.
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 artoo or surveycore.
ggpointless keeps adding the ggplot2 layers nobody else bothered to write.
mpactr spent two spring releases normalizing case in metadata after users kept tripping on it.
surveytidy taught every dplyr verb to operate on a whole collection of surveys at once.
PEIMAN2 cut its annotation database loose from its release cycle without breaking CRAN.
prospectr spent its biggest release in years fixing spectra it had been quietly mangling.
A German electricity load-profile package added gas and doubled the market it serves.
See all artoo alternatives → · See all surveycore alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — r-packages — within Infra & APIs. artoo 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. artoo 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 artoo alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "artoo alternatives" section above for the current picks, or visit /alternatives/artoo for the full list with editorial commentary on each.
Top surveycore alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "surveycore alternatives" section above for the current picks, or visit /alternatives/surveycore for the full list with editorial commentary on each.