• Git Bash
• Node.js

As an open source project, Brackets releases new features more often, so there is a slight delay between when a feature lands in Brackets vs. Brackets also integrates with a central community-managed registry for browsing and installing extensions. Brackets integrates Theseus, an open-source JavaScript debugger that enables developers to set break points, step through code, and inspect the value of variables in real time. Theseus can be used to debug any extension in Brackets and is easily installed using the built-in extension manager. With the majority (around 1/3rd) of votes Visual Studio Code is the winner. There were three other contestants in the poll, powerful Sublime Text (around 1/4th votes), furious Atom Editor (around 1/5th votes) and adorable Adobe Brackets (around 1/20th votes).

So hearing the news that Visual Studio Code is open-source, I started thinking it might actually be a good choice for a JavaScript IDE.

I just watched the introduction video that you'll first see when you visit this page: https://code.visualstudio.com/ It definitely has some things that I like, but I also noticed some things that made me cautious. So I'm asking people who've tried it about their experiences and maybe some advice.

Currently I'm a happy user of Sublime Text, so if someone has experience with both I'm especially eager to hear how they compare in your opinion.

The things I liked from the video that might pull me over:

• IntelliSense (obviously)

• Native debugger for Node.js apps

But these are the things that make me cautious:

• At 4:25 I see the guy add a TypeScript-specific comment inside a JavaScript file to instruct the editor how to handle Node.js definitions. Personally I really dislike it when I have to change my sources for the editor to be able to take full advantage of it. A project file or an external definitions file is no problem, but changes inside the code tick me off as it kinda ties the code to the IDE. But he also mentioned the editor is not 'project-based' but rather 'folder-based', which make me doubt whether it's possible to configure a project in such a way those comments inside the sources become unnecessary. Does anyone have insight into this?

• It seems the IDE is very tightly integrated, which can be a double-edged sword. For example, I want to use ESLint for linting and I use a build service that enforces the project contains no lint errors. But I got some projects that are still on JSHint. With Sublime Text I like that I can just install plugins for either and use whichever is appropriate. It is important to me the linting errors reported by my editor are the same that will be reported by my build service. To what extent does VSC allow you to configure various linters or does it force you to use its own? More generally, how's the plugin ecosystem coming along?

Some random questions:

• I know Microsoft is of course very much on the TypeScript train, and TypeScript is supposed to be an ES6 superset. Does anyone know how far they are in supporting ES6 features? Do the linter and IntelliSense correctly handle all ES6 features? How about upcoming ES7 features?

• What about JSX support?

Thanks for hearing me out, and looking forward to your thoughts :)

Mainly, which is actually better? I want to know which one to use for production and what are the actual differences between them. I'm going to be using Bootstrap in them.

peterflynn

3 Answers

As of November 2014 Adobe stopped further development of Edge Code and recommends to switch to brackets.

Source: https://creative.adobe.com/de/products/code

BijanBijan

Adobe Edge Code is a distribution of the Brackets open source project. It contains all the functionality of Brackets, plus additional extensions that integrate with other Adobe products like:

Edge Code uses the Creative Cloud desktop application to update in place. Brackets does not have an automatic update mechanism (yet).

As an open source project, Brackets releases new features more often, so there is a slight delay between when a feature lands in Brackets vs. Edge Code. Brackets also integrates with a central community-managed registry for browsing and installing extensions. Extensions must be manually installed into Edge Code.

Edge Code is dead. Adobe has stopped dev on it and recommends to switch to brackets.

Adobe edge code and brackets are both maintained by adobe. Edge Code is based on Brackets. If you are a Creative Cloud member, Edge is version is made special for you.

Here are some of the diffrences

1. You could call Brackets as the opensource and free where as Edge code is closed.
2. Edge code integrates well with adobe products where as Brackets does not do it out of box. Like this adobe.com/....
3. Brackets is updates more frequently (2-3 weeks) where as Edge is not that frequent.
4. Brackets has a linux(debian based) support but i did not find a mention for Edge but they may.
5. Being closed you get support from Adobe for edge.

If you have a Adobe CC licence go for Edge else Bracket is awesome enough.

As for as your question goes for bootstrap you could use any thing even Notepad or GEdit. production or not either doesn't make any difference.

aWebDeveloper

Git Bash

aWebDeveloper

Node.js

Not the answer you're looking for? Browse other questions tagged htmleditoradobeadobe-edgeadobe-brackets or ask your own question.