- Easily customizable
- Open Source
- Still in very early beta
- Requires installation
- Lack of split-screen support
- Lack of full-screen support
- No support for 3rd-party plug-ins
- No auto-completion
This is one area where I feel that Brackets stands alone. It’s an application that allows you to build upon it using itself! Quam frigidus est?
Because Brackets is built using HTML5 and CSS, it is rather easy to perfect the IDE to your exact liking without having to scour Google for the perfect syntax highlighter or application skin.
I’m not sure Adobe could have made it any easier to help develop and improve this platform. There is one small “gotcha” though:
So here’s the deal: Adobe has released this as open source, but under a modified version of the MIT license, which includes the following amendment:
Please note that some portions of this project are written by third parties
under different license terms. Your use of those portions are governed by
the license terms contained in the corresponding files.
Digging deeper, there’s a handful of other third-party libraries included in the project. The editor itself is driven by CodeMirror (which also powers JS Bin et JSHint). Also included in the source files is Twitter’s bootstrap et LESS, both of which are licensed under Apache 2.0. Be on the lookout for other third-party libraries as they are added to the project (though I would wager that Adobe’s legal team is also keeping an eye on the GitHub repo).
Still in very early beta
In Adobe’s own words, “It’s still very early in development, is missing a lot of basic editor features, et verisimile has bugs.” In my opinion, Brackets is at something of a catch-22—it’s still early beta, but if you do feel kind enough to contribute to the project, it will move along as fast as the projects GitHub managers can take in new pull requests. Personaliter, I had a difficult time getting it to run on Lion—it took a few tries to launch (do this directly from the project folder—don’t try dragging the executable to your Applications folder).
There’s a handful of usability issues that appear which most will find rather quickly I feel. Clicking—and even double clicking—folders within a given project will not expand that folder. You actually have to click on the arrow icon.
The main menu is also a bit off—you have to click to open each application menu (“File”, “Edit”, “View”, “Navigate”, etc.). What’s more—these menus exist outside of the default OS menu system. If Adobe is going to keep requiring a wrapper application, these menus should be integrated into the OS.
Denique, don’t bother right-clicking anything—there appears to be no existing context menu support.
One would assume that an editor built using HTML5 would be usable straight from a website (even if it does require a more modern browser with File API access), iustum? Infeliciter, that’s not the case. Brackets requires the use of a small native shell which wraps the entire application in order to access the local file system. Adobe links to a separate GitHub repo for this wrapper, but really they should just be linking to an installer. Allow me to save you the trouble: Click here to install Brackets.
Lack of split-screen support
Okay, so the TextMate has been lacking this for a while too. And you know what? That’s exactly why I now use Sublime Text 2 instead. Before switching entirely to Apple, I used to use Aptanaas my editor of choice on Windows. While editing HTML, css, and JS files at the same time, this becomes something of a requirement and once you have it, it’s extremely hard to let go of.
Lack of full-screen support
Not to sound like a broken record, but Sublime Text’s “Distraction Free” mode is a god-send in a world of constant instant messages, e-mails, Twitter, and Tumblr updates. Full-screen capabilities would be a most-welcomed addition.
No support for 3rd-party plug-ins
The best features of editors like Aptana, Code, Textmate, and Sublime Text are the ability to extend the editor with features that apply to specific developers with specific workflows. Although one can make the argument that because Brackets is open-source, these features can be added, in which case, where is the line drawn in order to prevent Brackets from becoming bloated with hundreds of features that the majority of users don’t require? As developers, we must live with the fact that plug-ins aren’t meant for everyone and that there will always be some amount of customization required to integrate an editor into our workflow.
Brackets definitely stands to become the wild card in the editor arena, especially so due to its potential to become one of the first (major) open source editors to the market. It has a long way to go, but if it gains enough critical mass from contributions from other developers, we poterat see this overtaking some of the more popular web editors, all of which currently seem to be vying for the #1 spot on their respective operating systems. Does Adobe’s dark horse have what it takes to come out on top?