You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
docs: reframe Brackets history to reflect community ownership
Clarify that the Phoenix Code project took over Brackets development
from Adobe, rather than implying a passive handoff. Simplify phrasing
and add "Brackets, reborn" tagline.
Copy file name to clipboardExpand all lines: blog/2026-03-04-phoenix-code-vs-brackets/index.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -39,11 +39,11 @@ The free version of Phoenix Code covers everything Brackets did and more — Git
39
39
40
40
## What Happened to the Brackets Editor?
41
41
42
-
Brackets was created at Adobe and built on CEF (Chromium Embedded Framework) — a technology choice that made sense in 2014 but became increasingly difficult to maintain. Security patches, OS compatibility, performance work — it all got harder every year. Adobe moved on in 2021, and the original Brackets entered maintenance mode with no further updates.
42
+
Brackets was created at Adobe and built on CEF (Chromium Embedded Framework) — a technology choice that made sense in 2014 but became increasingly difficult to maintain. Security patches, OS compatibility, performance work — it all got harder every year. In 2021, we took over Brackets from Adobe, continuing its development under the community we founded and now lead.
43
43
44
44
Rather than keep patching an aging foundation, we modernized the platform so it can run anywhere — in browsers, on desktop with Electron or Tauri, pretty much any modern system. One codebase that works everywhere, from [phcode.dev](https://phcode.dev) in your browser to a native desktop app.
45
45
46
-
The architecture changed. The team didn't. The design philosophy didn't.
46
+
The architecture changed. The team didn't. The design philosophy didn't. We named it Phoenix Code — Brackets, reborn.
47
47
48
48
---
49
49
@@ -53,7 +53,7 @@ If you're wondering whether Phoenix Code will feel familiar — it will.
53
53
54
54
**Live Preview** is still the core of the experience. Edit HTML or CSS and watch the browser update in real time, no manual refresh. This is the feature that defined Brackets, and it's still front and center.
55
55
56
-
**The lightweight workflow** is intact. Open a folder, start editing. No massive install, no mandatory plugins, no project configuration files to set up first.
56
+
**The lightweight workflow** is intact. Open a folder, start editing. Everything just works out of the box.
57
57
58
58
**Web-first focus.** HTML, CSS, JavaScript — that's the sweet spot. Phoenix Code is purpose-built for front-end work, not trying to be a general-purpose IDE.
59
59
@@ -111,7 +111,7 @@ Short version: open your project folder in Phoenix Code. That's it.
111
111
112
112
### What happened to the Brackets code editor?
113
113
114
-
Brackets was created at Adobe and actively developed until 2021. Adobe stopped maintaining it and the project entered maintenance mode. The same team that built Brackets continued the work as Phoenix Code — a full platform rewrite that runs in browsers and as a desktop app.
114
+
Brackets was created at Adobe and actively developed until 2021. The Phoenix Code project took over the development of Brackets, and rather than keep patching an aging foundation, we rebuilt it to run in browsers and as a desktop app. Brackets, reborn.
0 commit comments