Xi: an editor for the next 20 years [video] • Hacker News Board

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

#291

Post by alkonaut » Thu, Feb 01, 2018, 6:52 AM UTC

greglindahl wrote: post #289

alkonaut wrote: post #214

Earlier quoted context omitted.

you picked one that is already in that top. Try that with the 100th most used editor. I disagree it’s worth sticking to on text editor for programming tasks. The productivity boost of a good complex plugin is huge, way bigger than anything one gets from productivity in the text editing itself that comes from familitarity with the editor I think. Look at the state of e.g Rust dev in Atom/VSCode/.. today. It will get t…

Hey, you edited your comment to remove what I responded to. Thanks for not labeling the edit.

Probably realized just like you that I misinterpreted or formulated something poorly, sorry.

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

#292

Post by rplnt » Thu, Feb 01, 2018, 9:16 AM UTC

kakarot wrote: post #278

rplnt wrote: post #252

Earlier quoted context omitted.

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.

You should give PyCharm another go. If you don't have a license anymore, JetBrains offers a free community version. It is more than enough to suit my needs. What did you find bad about it? If it was just input latency, that's fixed.

The UI overall was slow (I wouldn't remember if input delay was part of it). It's been in 2012 or 2013 I think, so yeah, I would hope they got better at it :)

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

#293

Post by stormking » Thu, Feb 01, 2018, 10:16 AM UTC

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.

> What's the killer feature of iTerm these days?

Panes.

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

#294

Post by Jakob » Thu, Feb 01, 2018, 10:20 AM UTC

haskal wrote: post #287

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.

1. When you exit a terminal it dumps irrelevant stuff rather than just closing the tab. ~ % exit [Process completed] 2. Cmd + Arrow doesn't doesn't move to the next or last tab. (Cmd + number does work however, but it doesn't show numbers on the tab list like iTerm) 3. Comes with terrible defaults like the screen color.

There certainly are some advantages of iTerm2 but the ones you stated are very easily done in Terminal.app:

1. Settings > Profiles > Shell > When the shell exits: [Close the window|Close if the shell exited early|Don’t close the window]

2. macOS standard for all applications is the following.

  - next tab: ⌃⇥ or ⌘⇧]
  - previous tab: ⌃⇧⇥ or ⌘⇧[

If you really want to change that, you can do so in System Preferences

3. Settings > New window with profile: Pro

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

#295

Post by dmytrish » Thu, Feb 01, 2018, 1:01 PM UTC

stormking wrote: post #293

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.

> What's the killer feature of iTerm these days? Panes.

I don't use panes much, but Terminal.app seems to have panes too.

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

#296

Post by icedchai » Thu, Feb 01, 2018, 3:11 PM UTC

mailslot wrote: post #171

brucephillips wrote: post #109

Earlier quoted context omitted.

> 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.

If you think IntelliJ is bad, what do you think of Eclipse?

One of my worst IDE experiences was working on a Scala project in Eclipse, with a whole ton of plugins installed. Latency was incredibly high. It was like working on a lagged 300 baud terminal.

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

#297

Post by eropple » Thu, Feb 01, 2018, 4:32 PM UTC

dmytrish wrote: post #295

stormking wrote: post #293

Earlier quoted context omitted.

> What's the killer feature of iTerm these days? Panes.

I don't use panes much, but Terminal.app seems to have panes too.

- Bafflingly, they split horizontally. I have a 4x4 pane setup, but my default is 2x1.

- Cmd-W closes the window, not the pane. (I get why they do this. I feel that it is wrong.)

- I can't send input to all panes, which is a pretty useful feature I probably use once a week.

- iTerm2 happily maps my panes to tmux. This is by itself perhaps a killer feature.

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

#298

Post by mixmastamyk » Thu, Feb 01, 2018, 4:49 PM UTC

dhimes wrote: post #261

Retr0spectrum wrote: post #258

Earlier quoted context omitted.

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.

Yeah, but when you ask a Chinese person how to pronounce Xi or Xiu the X -> sh. That's why I went with Shee also when I read this.

Portuguese also.

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

#299

Post by erikb » Fri, Feb 02, 2018, 9:28 AM UTC

NoahTheDuke wrote: post #283

erikb wrote: post #272

Earlier quoted context omitted.

Thanks. However "z" is also not really a clear sound, right? "ds" or "ssss" or "tsss". Naturally I would interpret "zigh" very similar to "sigh" but since "sigh" is a real thing I think there is a reason why you write "zigh" instead. Anyway each hint is helpful. I'll google for that.

To help out, let me point you to the English phonology page on wikipedia: https://en.wikipedia.org/wiki/English_phonology . Specifically, look into the 'Voiced alveolar sibilant', the 'z' in English. That's the sound you're looking for, as it's the one used by Raph in the linked talk. For completeness, the vowel is the dipthong 'aɪ', pronounced like the 'i' in the word 'price', discussed on the same wiki page.

Great resource, thanks a lot! I think this is really the stuff you can't learn in high school education and have to learn by yourself. There our teachers are native Germans as well and while they are probably better than the average second language English learner they can't be perfect either.

In Chinese the "x" would be pronounced like that: https://en.wikipedia.org/wiki/Voiceless_alveolo-palatal_fric...

So not really a "sh-" either, but English doesn't have that sound at all I believe.

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

#300

Post by girvo » Fri, Feb 02, 2018, 3:05 PM UTC

lambdadmitry wrote: post #249

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.

Quake-style console. I'm too addicted to it unfortunately.

Literally the only reason why I use iTerm 2 over Terminal.app as well. Though I'm tempted to see if I can't replicate a similar "show over anything when a hotkey is pressed" in Terminal.app with some cute AppleScript...