If I may ask the author(s): what was the motivation of writing this app for native platforms but making use of webkit-node or similar technologies and tools? This to me seems like it has become a popular technique for writing cross-platform applications, but it also seems like it has many drawbacks which make it an unattractive option, with the only advantage being that the authors already know CSS/JS/HTML and can leverage that knowledge to make a protoduction-quality application. Can you confirm that this is the case, or was there some other reasons and/or factors that led to such a decision? Thank you for your time, and have a relaxing evening.
I wasn't there at the beginning, but I've been working on Brackets for a year.
We want Brackets to be awesome for web developers and designers specifically. So, how cool is it to be able to extend the editor you use every day using the exact same tech you're already used to? (And, of course, you can edit Brackets extensions in Brackets...)
This is likely part of the reason there are more than 200 extensions available for Brackets today.
