Hacker News Reader

Comment by ilaksh | Hacker News Reader

"Because it’s built in JavaScript, HTML and CSS, if you use Brackets, you have the skills necessary to customize, extend and contribute to it. Easy to fork and with a flexible and open license, it truly is your editor. In fact, when you first open Brackets you’ll be looking right at the Brackets source code. On the team, we use Brackets to develop Brackets in this weird inception-style-yin-and-yang type of thing."

My thing is like that too, especially the inception thing, but its better for a lot of reasons because its more than just an editor and is designed to be easily extended with plugins/components.

https://github.com/ithkuil/cureblog

https://vimeo.com/43784316

Anyway so good try Adobe, but if Adobe really wants to do the right thing, support the open web, and build a really useful tool, they should scrap Brackets, fork my project, and start promoting that. LOL sorry dickish thing for me to say but true.

View on HN

Judging by the git repo, brackets has been in development significantly longer than your project. It also seems much more complete already.

And your project doesn't seem to be designed as an IDE, but rather a blogging engine with a strange focus on code editing. How exactly are the projects similar?

After looking at the video on Vimeo it reminds more of Dave Winer's OPML Editor (http://home.opml.org/)

Thanks for looking at the video. One thing I should mention is that I have spent a day or so on the UI since then so it looks a lot more modern at the moment.

Anyway, I don't see how my project is related to OPML Editor really.. then again its not really easy to see the details of what that does from the web site.

But anyway my thing is about GUI controls that include the front and back end code and plugins to install them. GUI controls/widgets are an old and obvious and proven concept. The separation between front and back end coding, CSS and some other things that have happened with web development were practical approaches for awhile, but now with the web as platform, they are obviously a bit of a regression. There is just a very strong tradition now, a whole generation of CSSers and RESTers that just can't think any other way and unfortunately sometimes don't even talk to each other.

Widgets and plugins are a no-brainer.

So basically what we have confirmed is that I have more useful software development knowledge than the entire web team at Adobe.

Brackets probably has been in development longer and is more complete in a way. But the point is that although it goes a little bit in the right direction, it doesn't go far enough.

The code editor is a component that adds a button to the left hand side, which then opens up a window with CodeMirrors built in for editing the HTML/CSS/Browser side CoffeeScript/ Node.js on server side/external css/js files/package.json for the selected component. Then when you hit save it sends all of those files to the server, compiles CoffeeScript, runs npm if necessary. If there are errors it pops them up in a message box. If there are no errors it restarts the server and reloads the page. So it is an IDE.

Another similarity is the idea of keeping together different aspects of a component such as the HTML and CSS. I take it farther by including the other parts I mentioned above.

Blogging is just the most common type of application so I need to make sure it works for that for starters.

I don't think most bloggers are crying out for an IDE. I think that Adobe is trying to produce a platform/stack agnostic tool, whereas you aren't.

These are two different things. Might as well get mad at them for not building it on Eclipse.

Reply on news.ycombinator.com