They are focusing on memo. xray itself is on hold in the meantime.

It seems the last commit for memo was Feb 11 as well: https://github.com/atom/xray/tree/master/memo_core

I miss the updates 😢 They were so interesting!

I've been on paternity leave and come back April 1. I'm going to talk to leadership and get a sense for what's possible regarding continuing this work. Right now it's a bit unclear to me because I've been unplugged and the organization has been shifting following the acquisition.

Shifting in a good way?

Or a bad way? 😧

So much with the "Microsoft has changed". I just saw the "embrace, extend, and extinguish" strategy once again.

There is no doubt that microsoft has changed. Look at vscode, their contributions to nodejs etc. The question is how much and how the takeover might affect github and their current product lineup.

Xray was always an experiment and we were granted some runway to pursue it by leadership, which was awesome. It's clear that there's a future and use for Memo in current product thinking. Unfortunately, it doesn't seem like Xray as a whole is interesting to leadership right now. It's sad and I think it's a missed opportunity, but I also think it's understandable. Going forward, we'll need to make a decision about how to continue working on Memo in light of this reality. It may go back into its own repo. Still figuring this all out. Sorry everyone if this is disappointing. ❤️

@nathansobo thanks a lot for the update. I want to highlight one of the most exiting Xray's feature to me: a performant headless editor. With the growing adoption of remote environment, being able to connect to your dev machine from every imaginable device through the browser and share it live w/ your coworkers is invaluable, and I would say that there is quite some interest in that (e.g. https://github.com/codercom/code-server) – but at GitHub, you definitely are aware of this.

Said that you guys already did a lot and I appreciate it but letting Xray to die would be indeed a real pity! Is there maybe a possibility for the community to move this project forward, possibly with some guidance?

I'm not myself a Rust expert, but I'd love to get better at it, and with the right roadmap in mind, the "experiment" could keep going forward (hopefully with the help of other Stargazers too).

If not, it is also understandable.

Thanks again for your code! It has been a pleasure following the progress of this repo!

/cc @as-cii

As much as +1 comments are a thing of the past, I've come back to this repo regularly in the last few months, and ... so totally +1 for keeping it alive in some form!

I have also been checking back every few months and cheering at your progress.

I love Atom and VSCode but they both are laggy on a regular basis. I hope someone finds a way to keep things going.