Comparison to Xi

[davelab6]

I'm curious if you considered using xi editor as a base; its very similar to this roadmap

[mfournial]

I was also looking up on this today, as there is also XI-electron as a WIP.
I have a hackathon this weekend and was considering getting my team to work on this, trying to maybe merge the projects or advance on xray

[mfournial]

I was also looking up on this today, as there is also XI-electron as a WIP.
I have a hackathon this weekend and was considering getting my team to work on this, trying to maybe merge the projects or advance on xray

[nathansobo]

I had a conversation with @raphlinus yesterday about potentially combining efforts. It's clear we're converging on similar ideas and we want to keep talking, but we weren't ready to say for sure whether it makes sense to commit to that just yet. We have similar objectives, but they are far from identical.

So far, this project is just an experiment. We're planning to make some progress and see what we learn. We're open to it, but want to learn more about what the core of an Electron-specific setup might look like and pursue some of our own ideas before taking on the overhead of collaborating with another project.

[nathansobo]

I had a conversation with @raphlinus yesterday about potentially combining efforts. It's clear we're converging on similar ideas and we want to keep talking, but we weren't ready to say for sure whether it makes sense to commit to that just yet. We have similar objectives, but they are far from identical.

So far, this project is just an experiment. We're planning to make some progress and see what we learn. We're open to it, but want to learn more about what the core of an Electron-specific setup might look like and pursue some of our own ideas before taking on the overhead of collaborating with another project.

[raphlinus]

I also enjoyed the conversation with @nathansobo and feel it's worthwhile to continue exploring ways to work together. Some aspects, such as having a high performance Rust core and async coupling between the components, are very much in common between the two efforts. Other aspects, such as continuing to use Electron as the GUI toolkit, and having plugins in-process with FFI bindings rather than cross-process using RPC, represent different tradeoffs. I'm looking forward to continuing the exploration.

[raphlinus]

I also enjoyed the conversation with @nathansobo and feel it's worthwhile to continue exploring ways to work together. Some aspects, such as having a high performance Rust core and async coupling between the components, are very much in common between the two efforts. Other aspects, such as continuing to use Electron as the GUI toolkit, and having plugins in-process with FFI bindings rather than cross-process using RPC, represent different tradeoffs. I'm looking forward to continuing the exploration.

[JosephTLyons]

@nathansobo , I know you’ve said that this is only experimental as of now, but if everything goes according to plan, how do you see "x-ray" comparing to Atom?

[JosephTLyons]

@nathansobo , I know you’ve said that this is only experimental as of now, but if everything goes according to plan, how do you see "x-ray" comparing to Atom?

[nathansobo]

If everything went perfectly, I could see Xray as representing Atom 2.0. But I'm not prepared to commit to that happening. Transitioning the ecosystem would still be challenging socially even if we got everything right on a technical level. For now, you can think of this as Atom's equivalent of Servo. It's a place to experiment with what might be possible if we make some radical changes.

The README should cover most of what we're thinking. On a high level, it would be similarly extensible to Atom, but with much better performance and real-time collaboration baked into the core.

[nathansobo]

If everything went perfectly, I could see Xray as representing Atom 2.0. But I'm not prepared to commit to that happening. Transitioning the ecosystem would still be challenging socially even if we got everything right on a technical level. For now, you can think of this as Atom's equivalent of Servo. It's a place to experiment with what might be possible if we make some radical changes.

The README should cover most of what we're thinking. On a high level, it would be similarly extensible to Atom, but with much better performance and real-time collaboration baked into the core.

[hufan-akari]

There are many front-ends for the xi-editor.

Is it possible to build xray with different front-ends?
For example macOS native UI or system webview (yue/muban).

[hufan-akari]

There are many front-ends for the xi-editor.

Is it possible to build xray with different front-ends?
For example macOS native UI or system webview (yue/muban).

[nathansobo]

@hufan-akari We decided this week to change to a similar client/server architecture as Xi, although we're still planning on a more monolithic server. I talk about it in Monday's update, which isn't quite done yet but the draft is in #32. We only plan to maintain the web front-end, but we want to localize as much logic in the server as possible so it should definitely be possible to give it a different front end.

[nathansobo]

@hufan-akari We decided this week to change to a similar client/server architecture as Xi, although we're still planning on a more monolithic server. I talk about it in Monday's update, which isn't quite done yet but the draft is in #32. We only plan to maintain the web front-end, but we want to localize as much logic in the server as possible so it should definitely be possible to give it a different front end.