rtflite
rtflite stopped being an RTF writer and became the conversion layer for clinical table output.
Comparison · Analytics
qualtRics vs sass
A side-by-side editorial comparison of qualtRics and sass — release velocity, themes, recent moves, and the top alternatives to consider.
Shared themes:r-package
qualtRics vs sass: at a glance
What is qualtRics?
qualtRics moved its contact functions onto XM Directory days before the old endpoints died.
qualtRics is the R client for the Qualtrics v3 API — fetching survey responses, definitions, distributions, and contact lists into tidy data frames. Version 3.3.0 migrated all_mailinglists() and fetch_mailinglist() from the deprecated Research Core Contacts endpoints to XM Directory, ahead of Qualtrics retiring the old ones on June 30, 2026. Authentication and directory discovery are handled automatically, but the new endpoints return a different data shape, so column names changed. Before that, releases had been steady maintenance for two years, mostly around how survey response archives are unpacked.
What is sass?
Nine releases of compiler warnings and CRAN checks — the Sass binding is in pure upkeep.
sass compiles Sass to CSS for R, and its recent history is almost entirely about staying installable. The last ten releases are dominated by compilation warnings on new toolchains — Apple Clang 15, gcc-12, Windows — plus R CMD check fixes for r-devel and one LibSass version bump. The only user-visible changes in the set are the switch to woff2 font files in font_google(local = TRUE) and clearer output when Google fonts are downloaded.
qualtRics vs sass: editorial side-by-side
qualtRics
0.0ANALYTICS
qualtRics moved its contact functions onto XM Directory days before the old endpoints died.
◆ Current state
qualtRics is the R client for the Qualtrics v3 API — fetching survey responses, definitions, distributions, and contact lists into tidy data frames. Version 3.3.0 migrated all_mailinglists() and fetch_mailinglist() from the deprecated Research Core Contacts endpoints to XM Directory, ahead of Qualtrics retiring the old ones on June 30, 2026. Authentication and directory discovery are handled automatically, but the new endpoints return a different data shape, so column names changed. Before that, releases had been steady maintenance for two years, mostly around how survey response archives are unpacked.
◆ Where it's heading
This package's roadmap is set by Qualtrics, not by its maintainers, and the release history reads as a sequence of accommodations — endpoint changes, retired APIs, and edge cases in exported files. The team's own recurring theme is reducing surprise: caching was removed from fetch_survey() in 3.2.0 so results are never stale, error handling was standardized on retry semantics, and column mappings were made inspectable via extract_colmap(). Feature additions, when they come, are new endpoints wrapped rather than new abstractions.
◆ Prediction
With the Contacts migration complete, the next likely work is bringing the remaining Research Core-era functions onto XM Directory equivalents before Qualtrics retires more of the old surface.
sass
0.0ANALYTICS
Nine releases of compiler warnings and CRAN checks — the Sass binding is in pure upkeep.
◆ Current state
sass compiles Sass to CSS for R, and its recent history is almost entirely about staying installable. The last ten releases are dominated by compilation warnings on new toolchains — Apple Clang 15, gcc-12, Windows — plus R CMD check fixes for r-devel and one LibSass version bump. The only user-visible changes in the set are the switch to woff2 font files in font_google(local = TRUE) and clearer output when Google fonts are downloaded.
◆ Where it's heading
This is a stable binding to a C++ library that is itself no longer moving, so the package's work is defined by the compilers and CRAN policies around it rather than by Sass features. Nothing in these entries suggests active development; the maintenance is competent and prompt, but it is maintenance.
◆ Prediction
The next release will most likely be triggered by a new compiler warning class or an R CMD check requirement rather than by anything in the Sass language. The entries give no signal of planned feature work.
Alternatives to qualtRics and sass
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 qualtRics or sass.
git2rdata
git2rdata keeps sharpening one idea: a data frame that produces a readable git diff.
osmextract
osmextract stopped throwing your OpenStreetMap downloads away at the end of every session.
nanoparquet
nanoparquet is chasing byte-level agreement with the Java and Rust Parquet readers, not feature count.
poissonreg
poissonreg gave its models away to parsnip and kept the glue — now it just keeps glmnet honest.
S7
S7 has stopped adding surface and started proving it holds up against R itself.
See all qualtRics alternatives → · See all sass alternatives →
Recent activity from qualtRics and sass
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 1mo agoqualtRicsMailing list functions migrated to the XM Directory API ⚡
- 11mo agoqualtRicsZip extraction handles more special characters in survey titles
- 1y agosassPrivate finalize() on FileCache; clearer font download output
- 1y agoqualtRicsFix for questions with both recoded values and variable naming
- 1y agoqualtRicsBuild and CI housekeeping alongside the 3.2.1 release
- 2y agosassLocal Google fonts now downloaded as woff2
- 2y agoqualtRicsSurvey response caching removed from fetch_survey()
- 2y agosassFixes an R CMD check warning for r-devel
- 3y agosassSilences an Apple Clang 15 compilation warning
- 3y agosassRemoves a gcc-12 compilation warning on Windows
- 3y agosassBumps the bundled LibSass to 3.6.5
- 3y agoqualtRicsArgument checking refactor and include_* NA fix
Frequently asked questions
What is the difference between qualtRics and sass?
Both compete on the same themes — r-package — within Analytics. qualtRics and sass 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.
Is qualtRics better than sass?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. qualtRics and sass 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.
What are the best alternatives to qualtRics?
Top qualtRics alternatives in Analytics are ranked by recent ship velocity. Browse the "qualtRics alternatives" section above for the current picks, or visit /alternatives/qualtrics for the full list with editorial commentary on each.
What are the best alternatives to sass?
Top sass alternatives in Analytics are ranked by recent ship velocity. Browse the "sass alternatives" section above for the current picks, or visit /alternatives/sass for the full list with editorial commentary on each.