[kustosz]

Thank you for the feedback! To answer your concerns:

1. Studio is actually a set of plugins for Atom, not a fork. It's just that we are shipping an Atom binary and make sure that it can work alongside a standard Atom installation, for a smoother experience. We understand how many people use Atom for their daily work and we'd rather not mess with that.

2. That's a perfectly valid point! We'll prepare a CLI distribution, but for the first release we wanted to make sure that Studio works well (the visuality is one of the strongest points we're trying to make after all). For now there's an option to build a command line client from sources, but a bundled version is coming soon :)

[MadcapJake]

Regarding (1), this is a great way to distribute your language tooling. After a number of years using Atom, one thing that I've always wanted to see is a way to utilize multiple Atom instances all uniquely configured for a given use-case/language. For an editor that excels in customization, one thing Atom doesn't have is "profiles". I commend you for providing a Luna "profile" and I hope other languages/ecosystems consider using this approach.

[alexchamberlain]

I'd rather not be forced to use Atom...

[wdanilo]

@alexchamberlain Luna is not strongly connected to Atom. In fact, Luna gui runs in HTML and you are able to run it in your browser without Atom right now. However, we do not officially support it. We have chosen Atom just to bring a decent text editor to Luna Studio - thats it. We are planning to release web-based Luna version with some kind of web-text-editor in the future. It is not our priority right now (we want to focus on improving performance and delivering more rich data manipulators), however if you think you could help us with it, we would love to support it as much as we can!

What do you think about it?