Adobe Edge Code

» see html.adobe.com/edge/code as it lived, on the wayback machine

~ the obituary ~

edge code passed me by. by 2013 i was on sublime text 2 with a tabs-as-spaces preference set and a handful of go-to-line shortcuts memorized, and the adobe-branded version of a free open source editor was the wrong direction for what i wanted out of a code editor. edge code was the front-end-developer corner of the edge creative cloud bundle, a quick install for cc subscribers that wrapped the brackets project in an adobe header bar and an account login.

the project underneath was the interesting part. brackets started as an internal adobe project in 2011, went public on github by mid-2012, and got a slow community of contributors around the live-edit feature where a saved css change reloaded the page without a manual refresh. edge code was the marketing brand that adobe used to push the same editor inside creative cloud during the 2012 to 2014 window. one tree, two names.

the death announcement landed on the brackets blog on 4 november 2014 with a title that said welcome brackets 1.0. the second half of that post was the edge code goodbye. adobe wrote that brackets had reached the maturity bar the team originally set when the edge code branding was started, and that all future work on the editor would happen under the open source brackets name. cc subscribers were told to install brackets directly. edge code disappeared from the cc download page within a few weeks.

~ the case file ~

~ the climb ~

the edge family pitch in 2012 was that the photoshop-and-dreamweaver agency studio needed a set of html5 tools that did not feel like flash with a new logo. edge animate did the motion side, edge inspect did the device preview side, edge reflow did the responsive layout side, and edge code did the html-and-css editor side. on paper the suite was complete. in practice the components had different audiences and the cross-product workflow never really clicked.

edge code itself was popular in a small way. the live-edit feature was genuinely useful when you were tweaking a layout, and the extension model let people add language servers and lint configs before that vocabulary had spread. for a creative cloud user who did not want to learn sublime keybindings, the editor was a soft on-ramp into front-end work.

~ what got buried with it ~

brackets itself lived on for another seven years after edge code went away. the project kept shipping new builds, kept growing the extension catalog, and stayed on the recommended-editor list at design schools through the mid-2010s. adobe eventually handed maintenance to the brackets community in 2021 and stopped funding paid contributors, and the project moved to a smaller volunteer cadence after that.

the cleaner descendant was visual studio code. ms shipped vs code in 2015 with a similar electron base, a richer extension story from day one, and the github backing that brought language servers in fast. vs code took the air out of brackets in the same way brackets had taken the air out of dreamweaver as a code editor. edge code is now a small footnote in that handoff, a creative cloud experiment that ended cleanly the day its open source twin grew up.

@}-->--

              )
             (_)
            .-'-.
            |   |
            |   |
            |   |
            |   |
          __|   |__   .-.
       .-'  |   |  `-:   :
      :     `---'     :-'
       `-._       _.-'
           '""""""

« previous  ·  random  ·  next »