Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

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

recurse.com

Post reply on HN
Print view View original

251–260 of 306 posts

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

#251

Post by coldtea »

TheAceOfHearts wrote: post #221
postit wrote: 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…

Have you tried Terminal.app recently? A lot of people seem to rush immediately to iTerm2... And I used to be one of those, a few years back. But eventually I gave the built-in Terminal.app a serious chance and found it met all my requirements. Although I also stopped customizing my theme, and I keep as many defaults as possible. SF Mono is a great font!

>found it met all my requirements. Although I also stopped customizing my theme, and I keep as many defaults as possible

Well, if your requirements are low and the defaults are OK, sure, Terminal.app can do it. But iTerm2 does so many more things it's not even funny.

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

#252

Post by rplnt »

kakarot wrote: post #71
EddieRingle wrote: post #5

Earlier quoted context omitted.

You might be interested in this article from a JetBrains developer who implemented zero-latency typing in IDEA: https://pavelfatin.com/typing-with-pleasure/

I first switched to Webstorm in early 2016, on a Windows laptop at the time, and the latency was absolutely horrific. I'm talking 100-800ms. I was so off-put, even after changing a few settings, that I returned to Notepad++ for a while. I'd never been so disgusted at a piece of software. It's the 21st century and we're dealing with input latency in a text editor ??? Eventually they seemed to fix things and it started…

I bought (though in a sale) PyCharm few years back, without trying it much before (my bad), and found it really really bad. Used maybe 12 hours of my one year license.

Somehow got accustomed to to pretty much vanilla Sublime, mostly because I can't seem to get the language "intelligence" plugins to work correctly.

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

#253

Post by RandomCSGeek »

erikb wrote: post #239

Never I would have guessed that "xi" is pronounces "gsai". I would pronounce it "shee" (like chinese) or "ksai" (english) or "ksee" (german). Also, I don't thin we need another editor with a pluggable focus. It's not true that you need plugins to a text editor. It is plugged into an environment that also contains all the other things you need. It interacts via "open file", "read file", "write file" and "close file" w…

They say it's pronounced "Zigh". I am a non-native English speaker, so I am not even going to try to question this.

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

#254

Post by dsego »

mixmastamyk wrote: post #199
ryanmarsh wrote: post #22

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?

Never actually seen anyone use Atom, too slow everyone on HN said.

I see a lot of coder chicks on instagram pose with atom & react on their screens. It's become a fashion.

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

#255

Post by cmrdporcupine »

empath75 wrote: post #191
kakarot wrote: post #181

Earlier quoted context omitted.

You repeated the phrase different words. The question begged is Why does Google own the code?

Probably because he works on it on the clock.

Even if it's not on the clock, the open source contribution approval processs at Google is much easier (as another poster pointed out) if you just assign copyright to Google and host on the Google github (with the disclaimer that it's not official Google code).

It's actually a remarkably painless process, which is good because there's actually quite a bit of neat stuff in that neighbourhood of github as a result.

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

#256

Post by latexr »

MaxBarraclough wrote: post #242
TheAceOfHearts wrote: post #221

Earlier quoted context omitted.

Have you tried Terminal.app recently? A lot of people seem to rush immediately to iTerm2... And I used to be one of those, a few years back. But eventually I gave the built-in Terminal.app a serious chance and found it met all my requirements. Although I also stopped customizing my theme, and I keep as many defaults as possible. SF Mono is a great font!

I did the same thing a few years ago. Terminal.app has had tab support for years now. What's the killer feature of iTerm these days? I also recall finding Terminal.app to have lower CPU consumption, matching postit's experience.

Probably not a big feature for most, but I work with URLs in the terminal a lot and ⌘+click to immediately open them in the browser is convenient.

I prefer to open a new Terminal only when I need it instead of keeping one open all day (even if that sometimes happens) and I’ve never noticed an increase in CPU usage that’d made me want to check.

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

#257

Post by josteink »

jzoch wrote: post #226
Derbasti wrote: post #215

Earlier quoted context omitted.

How powerful are you planning your extensions to be? On a scale from Textmate (shortcuts that run shell scripts) to Emacs (you can implement Vim in Emacs), where would Xi's extensions stand?

Considering plugins can be written in any language and communicate via JSON, I'd posit they can be whatever you prefer. Turing-complete, even.

Coming from the Emacs side of things, I will have to call that an incomplete understanding of the concept of extensibility.

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

#258

Post by Retr0spectrum »

erikb wrote: post #239

Never I would have guessed that "xi" is pronounces "gsai". I would pronounce it "shee" (like chinese) or "ksai" (english) or "ksee" (german). Also, I don't thin we need another editor with a pluggable focus. It's not true that you need plugins to a text editor. It is plugged into an environment that also contains all the other things you need. It interacts via "open file", "read file", "write file" and "close file" w…

Almost every English word that starts with an X has a "z" sound. e.g. xenon, xylophone, xiphoid. In fact, I can't think of any exceptions.

"zigh" as a pronunciation seems natural to me.

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

#260

Post by bluerobotcat »

latexr wrote: post #256
MaxBarraclough wrote: post #242

Earlier quoted context omitted.

I did the same thing a few years ago. Terminal.app has had tab support for years now. What's the killer feature of iTerm these days? I also recall finding Terminal.app to have lower CPU consumption, matching postit's experience.

Probably not a big feature for most, but I work with URLs in the terminal a lot and ⌘+click to immediately open them in the browser is convenient. I prefer to open a new Terminal only when I need it instead of keeping one open all day (even if that sometimes happens) and I’ve never noticed an increase in CPU usage that’d made me want to check.

Terminal.app does that too
Post reply on HN