mlr3misc
The mlr3 utility belt has spent a year rebuilding how errors travel
A side-by-side editorial comparison of Appwrite and rappdirs — release velocity, themes, recent moves, and the top alternatives to consider.
| Feature | Appwrite | rappdirs |
|---|---|---|
| Sector | DevOps | DevOps |
| Velocity score | 10.0 | 0.0 |
| Sparks · 30d | 3 | 0 |
| Top themes | performance, cold-starts, developer-tooling, mcp | filesystem, config-paths, dependency, dormant |
| Last editorial update | 7h ago | 1h ago |
| Website | — | Visit → |
Appwrite is spending this quarter on latency: the CLI, cold starts, and now builds.
Appwrite Cloud is being tuned end to end for speed. The CLI was rewritten from Node to a single Go binary, function cold starts now mount a compressed SquashFS artifact instead of extracting files, and builds cache the package manager's store between runs. Alongside that, the MCP thread went both ways in a fortnight: Appwrite's own MCP server moved to a hosted remote endpoint, and a Functions template turned the platform into somewhere to host your own. Cloud economics are tightening in the background, with build and deployment storage billed from September 1 and scheduled executions jittered on Free and Education plans.
Load-bearing across CRAN, and untouched since January 2021.
rappdirs answers one question — where does an application put its data, cache and config on this operating system — and it has answered it the same way since 2014. The last release was 0.3.3 in January 2021, a revert of accidental vectorisation introduced four days earlier. The only substantive change in the package's visible history is 0.3.2 teaching user_data_dir(), use_cache_dir() and use_config_dir() to respect the R_USER_DATA_DIR, R_USER_CACHE_DIR and R_USER_CONFIG_DIR environment variables.
Appwrite Cloud is being tuned end to end for speed. The CLI was rewritten from Node to a single Go binary, function cold starts now mount a compressed SquashFS artifact instead of extracting files, and builds cache the package manager's store between runs. Alongside that, the MCP thread went both ways in a fortnight: Appwrite's own MCP server moved to a hosted remote endpoint, and a Functions template turned the platform into somewhere to host your own. Cloud economics are tightening in the background, with build and deployment storage billed from September 1 and scheduled executions jittered on Free and Education plans.
Every performance entry in this window targets the same path: the loop between a code change and a running deployment. Install time, extraction time, process start time — each is being removed in turn, with real before-and-after numbers rather than claims. That path matters most when something invokes it repeatedly, which is where the CLI rewrite and the MCP work point: CI pipelines and coding agents driving a project through its own tooling. The pricing changes run on a parallel track, drawing the line between what is free and what is guaranteed.
The cold-start work is currently limited to new deployments and favours larger artifacts, so extending it — or automating the redeploy it requires — is the obvious follow-up. The September 1 storage enforcement is dated and will land; expect deployment retention controls to get more attention as it approaches.
rappdirs answers one question — where does an application put its data, cache and config on this operating system — and it has answered it the same way since 2014. The last release was 0.3.3 in January 2021, a revert of accidental vectorisation introduced four days earlier. The only substantive change in the package's visible history is 0.3.2 teaching user_data_dir(), use_cache_dir() and use_config_dir() to respect the R_USER_DATA_DIR, R_USER_CACHE_DIR and R_USER_CONFIG_DIR environment variables.
Nothing is heading anywhere, and that is the finding. A port of a Python utility with no open direction, four releases in eleven years, and a dependency position underneath a large share of CRAN packages that need a cache directory. The 0.3.2 and 0.3.3 pair is instructive: a real improvement shipped alongside an accidental behaviour change that had to be reverted within the week, and then silence.
The entries give no basis for predicting a next release; on eleven years of evidence the most likely next change is a CRAN-mandated check fix rather than anything user-facing.
Other DevOps 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 Appwrite or rappdirs.
The mlr3 utility belt has spent a year rebuilding how errors travel
Zed ships weekly, and the Git surface is finally catching up to the agent surface
odbc keeps turning into an authentication broker with a database driver attached.
ps grew from a process inspector into the thing that reliably kills what you started.
wk spent one release fixing what empty means, then went quiet.
A package whose entire job is to ship someone else's database on time.
See all Appwrite alternatives → · See all rappdirs alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Appwrite is currently shipping more aggressively (velocity 10.0 vs 0.0), with 3 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. Appwrite is currently shipping more aggressively (velocity 10.0 vs 0.0), with 3 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other DevOps products to evaluate alongside.
Top Appwrite alternatives in DevOps are ranked by recent ship velocity. Browse the "Appwrite alternatives" section above for the current picks, or visit /alternatives/appwrite for the full list with editorial commentary on each.
Top rappdirs alternatives in DevOps are ranked by recent ship velocity. Browse the "rappdirs alternatives" section above for the current picks, or visit /alternatives/rappdirs for the full list with editorial commentary on each.