Live data from Hacker News

Xi: an editor for the next 20 years [video]

recurse.com

171–180 of 306 posts

Re: Xi: an editor for the next 20 years [video]

#171
post #82

Earlier quoted context omitted.

That's because you (probably) haven't used a modern text editor. If you'd follow either chrome's or firefox's changelog you'd also read about constant progress in optimizing their browser engine and dev tools.

> That's because you (probably) haven't used a modern text editor. Can you provide an example? Because I've worked on > 1MM line projects in IntelliJ with no performance issues, or at least none related to text editing.

IntelliJ is still slow even when I throw 12 cores Xeons at it.

... aside from the fact that I can compile some projects faster than it takes just to start up.

If IntelliJ were a car, it'd be gas guzzling SUV with a hole in the gas tank.

Re: Xi: an editor for the next 20 years [video]

#172

Presenter here, feel free to ask questions. Also thanks to the awesome Recurse Center for inviting me to speak and making the recording, and the audience for their great questions.

This is not an official Google product (experimental or otherwise), it is just code that happens to be owned by Google

Would you mind elaborating on this?

Re: Xi: an editor for the next 20 years [video]

#174
post #35

Earlier quoted context omitted.

Based upon momentum I believe the Electron based ecosystem has already won, yes. The momentum there eclipses... Eclipse, as well as many other closed and open source editors. If you don't see the Electron ecosystem as a winner today would you say they'll have won if all editors stay at their current momentum of new features and bug fixes?

10 years ago Eclipse was most popular editor and was considered the best. Java, C++, PHP. Aptana, IBM IDEs and many more. And now it is pretty much gone.

I really wonder what you are basing this opinion on. The most recent stable release (Oxygen) was released last June, and Eclipse Che, their cloud IDE last October. In Stack Overflow's 2017 Developer 2017, 20% of Web Developers use Eclipse, 25% of Desktop developers use Eclipse, 22% of SysAdmins use Eclipse, and 27% of Data Scientists and Engineers use Eclipse.

Re: Xi: an editor for the next 20 years [video]

#175
post #82

> modern text editor with uncompromising performance Solution in search of a problem. I haven't run into an editor performance issue in more than twenty years. I will gladly trade a hundred text editor performance fixes for one web browser performance fix .

That's because you (probably) haven't used a modern text editor. If you'd follow either chrome's or firefox's changelog you'd also read about constant progress in optimizing their browser engine and dev tools.

So your definition of "modern text editor" == "built on a web browser"?

I certainly wouldn't consider any of those toys to be more modern than vim, sublime, emacs, etc. Newer maybe, but not more modern.

Re: Xi: an editor for the next 20 years [video]

#177

Presenter here, feel free to ask questions. Also thanks to the awesome Recurse Center for inviting me to speak and making the recording, and the audience for their great questions.

This is not an official Google product (experimental or otherwise), it is just code that happens to be owned by Google Would you mind elaborating on this?

not the op. just my understanding is that it is raphlinus's code. It means Google has literally nothing to do with it, other than happening to own the code.

(IE it's not an experimental product, it's not a product at all. It's just raphlinus releasing some code)

Re: Xi: an editor for the next 20 years [video]

#179

Great stuff, and awesome to see this coming from Google (and in Rust instead of Go). Interesting historical note: The author of Sublime Text left Google to work on it by himself when he couldn't get it approved as a 20% project.

It is not "coming" from Google despite it is under Google GitHub organization. There is a disclaimer[1] at the bottom of the repo README, stating that "This is not an official Google product (experimental or otherwise), it is just code that happens to be owned by Google.". It's my understanding that it's Raph code and Google has nothing to do with it other than having to own the code.

[1] : https://github.com/google/xi-editor#disclaimer

Re: Xi: an editor for the next 20 years [video]

#180
post #18

Earlier quoted context omitted.

I must concur. With an equivalent vim setup and code files, nothing beats X11/suckless terminal on my OpenBSD machine. Comparing to that, even Alacritty looks like a slug. I must say however that things are looking a bit better in iTerm2 when switching the Metal renderer on. It's just a shame that an Nvidia GPU on OSX is necessary to compete with my $1000 Lenovo with its crappy Intel chip on OpenBSD when it comes to…

iTerm2's design is saddled by some history. At the time I took it over, everything was done in a single thread. By the time I realized I was going to stay with the project and how bad the design was, it was too late to change it. I've moved as much work as possible off the main thread (parsing the bytestream and now rendering). I think Terminal gets very nice performance without resorting to Metal by doing only UI wo…

Did you hit any pain points using Metal?
Post reply on HN