rollupTree
The recursive-computation engine under massProps grows the accessors its consumer needed
Comparison · Infra & APIs
ShortForm vs writeAlizer
A side-by-side editorial comparison of ShortForm and writeAlizer — release velocity, themes, recent moves, and the top alternatives to consider.
ShortForm vs writeAlizer: at a glance
What is ShortForm?
Automated scale shortening with lavaan, spending its releases repairing its own search algorithms.
ShortForm automates the creation of short-form psychometric scales by searching for well-fitting subsets of items, using ant colony optimization, simulated annealing and Tabu search over lavaan models. The recent releases are corrective: 0.5.7 fixed the ant colony algorithm failing to update its best model and the simulated annealing routine mis-specifying models containing factor relationships or outcome variables, and 0.5.8 fixed Tabu search under parallel workflows and with multidimensional models. Each release note carries an explicit roadmap listing refactoring for 0.6.0 and input standardisation for 0.7.0, neither of which has shipped.
What is writeAlizer?
Six months of releases and not one of them touched the scoring models
writeAlizer generates predicted writing-quality scores from features produced by Coh-Metrix, ReaderBench and GAMET, downloading its trained scoring models on demand. Every release in this window — nine of them between September 2025 and February 2026 — is about that download path rather than the scoring: classed error conditions, checksum verification, an offline mode, a mockable artifact directory, and dependency reporting for the model families a user actually invokes.
ShortForm vs writeAlizer: editorial side-by-side
ShortForm
0.0INFRA · APIS
Automated scale shortening with lavaan, spending its releases repairing its own search algorithms.
◆ Current state
ShortForm automates the creation of short-form psychometric scales by searching for well-fitting subsets of items, using ant colony optimization, simulated annealing and Tabu search over lavaan models. The recent releases are corrective: 0.5.7 fixed the ant colony algorithm failing to update its best model and the simulated annealing routine mis-specifying models containing factor relationships or outcome variables, and 0.5.8 fixed Tabu search under parallel workflows and with multidimensional models. Each release note carries an explicit roadmap listing refactoring for 0.6.0 and input standardisation for 0.7.0, neither of which has shipped.
◆ Where it's heading
The defects being fixed are in the search itself rather than around it. An optimizer that does not correctly retain its best candidate, and a search that mis-specifies models after the first iteration, both produce plausible-looking short forms that are not the ones the method should have found, which is a harder class of problem to notice than a crash. Alongside that the package is shedding dependencies, with ggplot2, ggrepel and tidyr dropped from the plotting methods in 0.5.8. The stated intent to refactor the major functions and standardise their arguments suggests the maintainer regards the current interface as the obstacle to further work.
◆ Prediction
The roadmap repeated across these notes points to a 0.6.0 focused on refactoring the major functions, with argument and output standardisation deferred to 0.7.0. On the evidence of this window, more unit tests and further algorithm-level fixes are likelier to arrive first than either milestone.
writeAlizer
0.0INFRA · APIS
Six months of releases and not one of them touched the scoring models
◆ Current state
writeAlizer generates predicted writing-quality scores from features produced by Coh-Metrix, ReaderBench and GAMET, downloading its trained scoring models on demand. Every release in this window — nine of them between September 2025 and February 2026 — is about that download path rather than the scoring: classed error conditions, checksum verification, an offline mode, a mockable artifact directory, and dependency reporting for the model families a user actually invokes.
◆ Where it's heading
The package is being made safe to distribute. CRAN's policy on packages that reach the internet drove the first wave — graceful failure, tests that preflight their URLs and skip, examples seeded from a local mock model — and 1.7.0 turned the accumulated fixes into structure with named error classes for each failure mode. Only 1.7.2 adds anything a user would ask for: filename handling for Coh-Metrix and GAMET outputs that arrive as paths.
◆ Prediction
With the artifact registry hardened and documented, the pressure that produced nine releases in six months should ease, and attention can return to the models themselves — the vignette on scoring-model development added in 1.7.2 hints at that. Nothing here promises new models.
Alternatives to ShortForm and writeAlizer
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 ShortForm or writeAlizer.
massProps
A mass-properties rollup spends a year on documentation and follows its sibling's API
samplr
A cognitive-science sampling package ships once, then goes quiet for eighteen months
stochvol
A Bayesian volatility sampler in its maintenance decade, paying for its own speed
midr
A black-box interpreter reaches CRAN, then learns multi-class and survival responses
GeoThinneR
Spatial thinning grows a result object, and the API breaks to make room for it
See all ShortForm alternatives → · See all writeAlizer alternatives →
Recent activity from ShortForm and writeAlizer
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 3mo agoShortFormTabu search fixed for parallel and multidimensional models
- 3mo agoShortFormAnt colony search failed to retain its best model
- 6mo agowriteAlizerOne example rewrapped to silence a CRAN check note
- 8mo agowriteAlizerFilename stems recovered from Coh-Metrix and GAMET paths
- 10mo agowriteAlizerOffline example guard, declared as no API change
- 10mo agowriteAlizerNamed error classes for every model-download failure mode
- 10mo agowriteAlizerNetwork failures degrade gracefully under CRAN policy
- 11mo agowriteAlizerwa_seed_example_models() exported and documented
- 1y agoShortFormlavaan model specification defaults made forgiving
- 2y agoShortFormCompatibility fixes for a new lavaan release
- 2y agoShortFormAdapted to changed lavaan error and warning messages
- 2y agoShortFormDefault specification tweaks and documentation fixes
Frequently asked questions
What is the difference between ShortForm and writeAlizer?
They serve adjacent needs but don't currently overlap on shipped themes. ShortForm and writeAlizer 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 ShortForm better than writeAlizer?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. ShortForm and writeAlizer 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.
What are the best alternatives to ShortForm?
Top ShortForm alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "ShortForm alternatives" section above for the current picks, or visit /alternatives/shortform for the full list with editorial commentary on each.
What are the best alternatives to writeAlizer?
Top writeAlizer alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "writeAlizer alternatives" section above for the current picks, or visit /alternatives/writealizer for the full list with editorial commentary on each.