Xray's Intent?

[JosephTLyons]

I suppose I'm still a little unclear on the exact intent of Xray. You'll have to forgive me, much of the lingo tossed around in the updates goes directly above my head. Is it meant to be a desktop editor that is developed independently of Atom, a desktop editor meant to replace Atom? A web-based editor only (maybe Github's own cloud editor for Github users to code with - a cool idea!)? Will Atom packages be compatible with X-ray, or will it require an entirely new package ecosystem? If I understand correctly, all of this is mostly experimental, but if it succeeds in being a useful tool, where is this tool going to thrive? It is very exciting to read the updates and see the progress, as the code editor is the developer's favorite and most used tool, so I'm really curious to know where this is all heading. :)

Sorry for using a pull request, I closed it so that it wouldn't be in the way of real issues.

[nathansobo]

Hi @JosephTLyons,

You're right that first and foremost, Xray is still a testbed for experimentation, and we ourselves are not completely clear on exactly where it's headed. All of the options you mention are a possibility, but the focus for now is on innovating in the realm of version control and exploring new approaches to in-browser editing. Atom package compatibility is explicitly not a priority and is unlikely to become one.

[JosephTLyons]

Knowing that Atom packages most likely won't be supported leaves me wondering if there will be any package system (in the event that X-ray becomes a native desktop editor). At any rate, I'm very excited to see how it pans out.

[Arcanemagus]

@JosephTLyons Extensibility is one of the Foundational Priorities so I'd say it's a pretty safe bet there will be some sort of system 😉.