Earlier quoted context omitted.
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)
You repeated the phrase different words. The question begged is Why does Google own the code?
Xi: an editor for the next 20 years [video]
191–200 of 306 posts
Re: Xi: an editor for the next 20 years [video]
#192Earlier quoted context omitted.
You repeated the phrase different words. The question begged is Why does Google own the code?
It is much easier as a Google employee to publish open source projects under Google's copyright[0] rather than getting them to grant the copyright to you. To have Google give you (the Google employee) full copyright of projects you work on while at Google, you need to go through a committee[1] that reviews the project to make sure it doesn't collide with some other project Google already is working on. As this is rea…
Re: Xi: an editor for the next 20 years [video]
#193Re: Xi: an editor for the next 20 years [video]
#194Just today I was trying to edit a 15MB JSON file and it was so terribly slow with Sublime Text and wondered if there was something faster out there. Edit: So I built Xi-Mac and the file opens in a fraction vs ST3 but once it's open performance is just as bad or maybe even worse.
Re: Xi: an editor for the next 20 years [video]
#195There 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 w…
Re: Xi: an editor for the next 20 years [video]
#196Earlier quoted context omitted.
I've got an unrelated question about tmux/iTerm2 - hope you don't mind me asking. I'm a heavy iTerm2 user and always been curious about tmux. Is there any reason to try out tmux integration if I'm already comfortable with iTerm2's features and panelling? I kind of got the impression tmux integration was largely for people who love tmux and are migrating to iTerm2, so it just makes it more familiar. Or is it something…
Not at all, if only to tell about virtues iTerm2 and tmux to wider audience! Short version: iTerm with tmux control mode (tmux -CC flag) is still iTerm, only now with tmux benefits like persistent shell sessions. iTerm translates regular commands like new window and split pane into tmux commands and acts otherwise like regular iTerm. Mac might crash or SSH get disconnected and tmux stays running to save you from losi…
Re: Xi: an editor for the next 20 years [video]
#197Just today I was trying to edit a 15MB JSON file and it was so terribly slow with Sublime Text and wondered if there was something faster out there. Edit: So I built Xi-Mac and the file opens in a fraction vs ST3 but once it's open performance is just as bad or maybe even worse.
Is this a debug build or a release build? File loading isn't particularly fast atm (we load the whole file into memory) but once a file is open I can breeze through it..
It's painfully slow, moving the cursor 1 character to the right takes like 10 seconds.
Do you want me to file a bug?
Re: Xi: an editor for the next 20 years [video]
#198Earlier quoted context omitted.
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)
You repeated the phrase different words. The question begged is Why does Google own the code?
Re: Xi: an editor for the next 20 years [video]
#199Earlier 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?
Re: Xi: an editor for the next 20 years [video]
#200Earlier quoted context omitted.
Caching is great but it doesn’t help you when paging through a big file where the entire screen contents get replaced on each update. Is that not what you benchmark?
That is correct. I'm measuring scrolling at low to medium speeds, where the majority of the text hasn't changed (this also corresponds to most editing tasks). I don't want to make the claim that I'm keeping up when scrolling at very high speeds. I think my assumptions are reasonable for an editor, but for a terminal scrolling at high speed is much more common. I have certainly considered fast-pathing monospaced font…