[DISCUSSION] Landing livedev2 in Brackets

[busykai]

This is a follow up to this @redmunds and @sebaslv discussion here. We need to figure out how we want to land this extension in the mainstream Brackets. While everybody's busy with the 1.0 release, @sebaslv and I could start working on actually landing the extension in the editor. We have to agree on which of the options is the way we want to go. There are a few options as I see them:

1. Keep the extension completely separate and make it a drop-in replacement.
2. Integrate it as an extension (could be a sub-module or copied code).
3. Copy the code next to existing LiveDevelopment. In a sense, this code will cease to be an extension and will be an optional (experimental?) version of LD. The users would switch between them (via UI or prefs), depending on what they want to use it for.

I like the 3rd option the best -- it puts this implementation on par with the existing one and allows us to reorganize the existing LD code to share it more efficiently. Also, it will make our lives easier when later we would want to make this version the "mainstream" one.

There's also some code which has not been contributed yet because we don't have a decision. E.g. browser launch (we have implementation for Firefox and Chrome in JS, in Brackets it's done via shell for Chrome only), enabling live development on remote machines (there's some demand for that in Brackets as well, requires changes in core editor). Let's discuss what's the best approach to this.

@dangoor, @redmunds, @njx, @sebaslv. Anybody I'm missing?

[dangoor]

I like option 3. Probably just putting the new code behind a pref until we're ready to cut over.