mlr3misc
The mlr3 utility belt has spent a year rebuilding how errors travel
Comparison · DevOps
Appwrite vs xfun
A side-by-side editorial comparison of Appwrite and xfun — release velocity, themes, recent moves, and the top alternatives to consider.
Appwrite vs xfun: at a glance
| Feature | Appwrite | xfun |
|---|---|---|
| Sector | DevOps | DevOps |
| Velocity score | 10.0 | 0.0 |
| Sparks · 30d | 3 | 0 |
| Top themes | performance, cold-starts, developer-tooling, mcp | utilities, publishing, headless-browser, litedown |
| Last editorial update | 7h ago | 1h ago |
| Website | — | Visit → |
What is Appwrite?
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.
What is xfun?
Yihui's utility grab-bag is quietly growing a web server and a headless browser.
xfun is the shared utility layer under knitr, rmarkdown, bookdown and litedown, and its recent releases cluster in three places: the record() function that captures code output for litedown, a local app-serving stack built on R's internal httpd, and a headless-browser toolkit. Version 0.58 replaced direct httpd routing with a proxy and added serve_dir() and random_port(); 0.55 added browser_print() and 0.60 added browser_dom(), which runs JavaScript on a page and returns the rendered DOM.
Appwrite vs xfun: editorial side-by-side
Appwrite
10.0DEVOPS
Appwrite is spending this quarter on latency: the CLI, cold starts, and now builds.
◆ Current state
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.
◆ Where it's heading
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.
◆ Prediction
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.
xfun
0.0DEVOPS
Yihui's utility grab-bag is quietly growing a web server and a headless browser.
◆ Current state
xfun is the shared utility layer under knitr, rmarkdown, bookdown and litedown, and its recent releases cluster in three places: the record() function that captures code output for litedown, a local app-serving stack built on R's internal httpd, and a headless-browser toolkit. Version 0.58 replaced direct httpd routing with a proxy and added serve_dir() and random_port(); 0.55 added browser_print() and 0.60 added browser_dom(), which runs JavaScript on a page and returns the rendered DOM.
◆ Where it's heading
The package is accreting the infrastructure Yihui's publishing tools need rather than staying a pile of small helpers. Serving directories, allocating ports, proxying the help server, driving a headless browser and printing to PDF are all pieces of one pipeline: render R output to HTML, then get it onto a screen or into a static file without a heavyweight dependency. The rest of the release stream is release-automation tooling for the author's own CRAN workflow and a long tail of parser bug fixes in taml_load().
◆ Prediction
Expect the browser functions to consolidate into a documented interface used directly by litedown, and expect cache_rds() to be fully retired in favour of cache_exec() now that it is no longer recommended.
Alternatives to Appwrite and xfun
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 xfun.
Zed
Zed ships weekly, and the Git surface is finally catching up to the agent surface
odbc
odbc keeps turning into an authentication broker with a database driver attached.
rappdirs
Load-bearing across CRAN, and untouched since January 2021.
ps
ps grew from a process inspector into the thing that reliably kills what you started.
wk
wk spent one release fixing what empty means, then went quiet.
See all Appwrite alternatives → · See all xfun alternatives →
Recent activity from Appwrite and xfun
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 18h agoAppwriteUp to 4x faster dependency installs with the build cache
- 1d agoAppwriteFaster cold starts for Appwrite Sites and Functions with SquashFS
- 2d agoAppwriteThe Appwrite CLI is now written in Go ⚡
- 6d agoAppwriteScheduled executions shift slightly on Free and Education plans
- 7d agoAppwriteDeploy your own MCP server with the new Functions template ⚡
- 10d agoAppwritePricing update: storage costs for builds and deployments will be enforced ⚡
- 1mo agoxfunbrowser_dom() added; Windows silently truncated self-contained HTML
- 1mo agoxfunpost_release() automates post-CRAN chores; nested math fixed
- 2mo agoxfunnew_app() moves to a proxy; serve_dir() and random_port() added ⚡
- 4mo agoxfunLiteral JavaScript in tojson(); record() bottleneck fixed
- 6mo agoxfunDeprecated attr() and qs support removed; parallel rev_check
- 8mo agoxfunbrowser_print() opens the headless-browser path
Frequently asked questions
What is the difference between Appwrite and xfun?
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.
Is Appwrite better than xfun?
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.
What are the best alternatives to Appwrite?
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.
What are the best alternatives to xfun?
Top xfun alternatives in DevOps are ranked by recent ship velocity. Browse the "xfun alternatives" section above for the current picks, or visit /alternatives/xfun for the full list with editorial commentary on each.