Live data from Hacker News

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

recurse.com

41–50 of 306 posts

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

#41

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.

Where is the Xi plugin documentation (as in, how to write and install a plugin, what are the APIs).

I found https://github.com/google/xi-editor/blob/master/doc/plugin.m... , but it doesn't have anything technical (or a tutorial).

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

#42
post #2

There finally starts to be consciousness about input and output latency for GUI applications. Xi sounds like an editor I'd love to use. Latency while typing is a jarring experience.

> Latency while typing is a jarring experience.

This is so true.

I grew up on the Commodore 64. The machine was usually pretty responsive, but when I typed too quickly in my word processor it sometimes got stuck and ate a few characters. I used to think: "If computers were only fast enough so I could type without interruption...". If you'd asked me back then for a top ten list what I wished computers could do, this would certainly have been on the list.

Now, 30 years later, whenever my cursor gets stuck I like to think:

"If computers were only fast enough so I could type without interruption..."

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

#43

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.

Where is the Xi plugin documentation (as in, how to write and install a plugin, what are the APIs). I found https://github.com/google/xi-editor/blob/master/doc/plugin.m... , but it doesn't have anything technical (or a tutorial).

It's still a work in progress, we're revving the plug-in protocol. I'm looking forward to the time we can point people to a stable interface, but sadly it's not there yet.

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

#44
post #38

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.

Why the name?

I wanted something short, and it felt kinda futuristic. The similarity to "vi" was also intentional.

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

#45
post #38

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.

Why the name?

(Not the author) I presume a reference to one the many mathematical/scientific usages? https://en.wikipedia.org/wiki/Xi_(letter)#Mathematics_and_sc...

I particularly like the "No change of state" meaning in "Z notation", apparently a formal language for specifying and modeling computer systems.

Edit: never mind, author beat me and debunked my overly-complicated analysis

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

#46
post #20

Earlier quoted context omitted.

You named some random things that have been around for short periods of time and claimed that "they won". I don't get it.

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?

Here, you can have your cake (electron) and eat it too (xi-core) https://github.com/acheronfail/xi-electron

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

#47
Pragmatically speaking the issue with switching editors is the fact that if it is not emacs or vi it is not a default install on whatever you sit down at.

I have tried tons of editors, and I always come back to vim. Heck, I have even moved my .vimrc to be the simplest possible with the smallest number of plugins.

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

#48

Xi looks great, has a very clever design, and clearly is a next generation platform for building a useful and powerful editor. I'd love to see this project continue and be a success. I think there is plenty of room for yet another text editor. Here's where I'm going to be a bit of a party pooper. Pragmatically speaking all of the great stuff Raph is talking about doesn't really matter. What Raph cares about are the k…

There's a reason there are hundreds of text editors and only a handful of remaining general-purpose desktop operating system and only a handful of remaining microprocessor ISAs.

In the 1980s and 1990s the i386 ISA had tremendous velocity, which is why it still exists whereas DEC Alpha does not. In contrast, to the situation with microprocessor ISAs, it is practical to use a text editor without a lot of velocity -- or at least it is practical for me because of the way I use my text editor: basically, I just want something with a clean internal architecture that is as easy for me to learn how to modify as Emacs currently is.

Modifying or customizing vscode has a low barrier to entry only if you already know web technologies. if you do not, then it has a very high barrier to entry compared to most other text editors.

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

#49
post #9

Xi creator did an amazing work implementing ropes ( https://github.com/google/xi-editor/tree/master/rust/rope ) The design documents ( https://github.com/google/xi-editor/tree/master/doc/rope_sci... ) explaining the concepts and implementation details is a must for those who want to understand its core. But I still have my regards regarding input latency being accredited only to the text editor. I recently switched b…

Yeah iterm2 is pretty unacceptable. For me alacritty is still missing some polish (i.e. text size keeps on changing when I attached/detach monitors), but it's really solid for using nvim.

I've actually been using nvim as my terminal multiplexer instead of using tmux.

Post reply on HN