Eclipse Theia
A monthly IDE-platform cadence whose release notes list contributors, not changes.
A side-by-side editorial comparison of Zed and Frappe Framework — release velocity, themes, recent moves, and the top alternatives to consider.
Zed just put its agent's terminal behind a sandbox, and that changes what it can be trusted with.
Zed ships weekly, mixing editor craft with steady agent work. The current release sandboxes the Agent's terminal commands and web fetches, adds undo and redo for Project Panel file operations, a Skip Hooks commit option, and configurable Agent Panel fonts. Recent weeks brought llama.cpp as a language model provider, Claude Opus 5 and GPT 5.6 support across BYOK providers, staged and unstaged multibuffers for hunk-level review, Git Graph improvements, and the move of LLM providers, external agents, and MCP servers into the settings editor.
Two release trains, one direction: v16 absorbs what CRM and Helpdesk built themselves.
Frappe runs two trains in parallel — v15 as the maintained stable line, v16 as the next major — and the same change often lands in both within hours. The v15 entries are almost entirely permission and export correctness. The v16 entries carry the new surface: a grouped settings dialog, a Recorder timeline showing how long each document action took and which apps were involved, and Cloud Settings inside Desk. The notes are LLM-generated and the feed says so.
Zed ships weekly, mixing editor craft with steady agent work. The current release sandboxes the Agent's terminal commands and web fetches, adds undo and redo for Project Panel file operations, a Skip Hooks commit option, and configurable Agent Panel fonts. Recent weeks brought llama.cpp as a language model provider, Claude Opus 5 and GPT 5.6 support across BYOK providers, staged and unstaged multibuffers for hunk-level review, Git Graph improvements, and the move of LLM providers, external agents, and MCP servers into the settings editor.
Two threads run in parallel and are starting to meet. The Git work has been building toward review-inside-the-editor — hunk staging, graph columns, branch picker filtering — while the agent work has been building toward an agent that operates on the repository rather than suggesting text. Sandboxing is the gate between those: an agent that runs terminal commands and fetches URLs needs containment before anyone lets it work unattended. Adding llama.cpp alongside hosted providers and moving provider configuration into settings both point at model choice being treated as user configuration rather than product identity.
Expect the sandbox to gain user-visible policy — which commands or hosts an agent may reach — since containment shipped before any controls over what it permits.
Frappe runs two trains in parallel — v15 as the maintained stable line, v16 as the next major — and the same change often lands in both within hours. The v15 entries are almost entirely permission and export correctness. The v16 entries carry the new surface: a grouped settings dialog, a Recorder timeline showing how long each document action took and which apps were involved, and Cloud Settings inside Desk. The notes are LLM-generated and the feed says so.
The clearest pattern is consolidation. Features CRM and Helpdesk built on top of the framework — forms, phone number fields, notifications, activity history — are being pulled down into v16 so the apps stop carrying their own copies. Running alongside it is a steady tightening of the permission model: link fields respect read rights, child-table lookups check the parent document, Report scripts are restricted to approved methods. Frappe is being hardened as the platform its own apps sit on, not extended outward.
Expect more app-level features to move down into the v16 shared layer as it fills out, with v15 continuing to take only permission and export fixes until v16 is ready to take over.
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 Zed or Frappe Framework.
A monthly IDE-platform cadence whose release notes list contributors, not changes.
Skaffold ships a minor a month and tells you nothing about any of them.
Eclipse Che is answering the one objection to cloud dev environments: your uncommitted work survives.
ActiveMQ is shrinking its own defaults — servlets off, factories blocked, frames capped.
gRPC just made post-quantum key exchange the TLS default — no flag, no opt-in.
Protobuf is loading Edition 2026 with enforced defaults, one release candidate at a time.
See all Zed alternatives → · See all Frappe Framework alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Zed is currently shipping more aggressively (velocity 7.5 vs 5.0), with 1 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. Zed is currently shipping more aggressively (velocity 7.5 vs 5.0), with 1 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 Zed alternatives in DevOps are ranked by recent ship velocity. Browse the "Zed alternatives" section above for the current picks, or visit /alternatives/zed for the full list with editorial commentary on each.
Top Frappe Framework alternatives in DevOps are ranked by recent ship velocity. Browse the "Frappe Framework alternatives" section above for the current picks, or visit /alternatives/frappe-framework for the full list with editorial commentary on each.