For most code work that’s probably not a situation to optimise for, but I often work on large markup documents.
Zed, a collaborative code editor, is now open source
181–190 of 642 posts
Re: Zed, a collaborative code editor, is now open source
#182> respond to your keystrokes on the next display refresh Claimed insertion latency for a keystroke: - zed 58ms - subl 75ms - vscode 97ms - clion 83ms 60 Hz displays refresh once every ~16.6ms. 58ms to insert a character is ~3.5 frames. My laptop can do 120 Hz, and other monitors can even do 300 Hz. Yeah, it's a lot faster than the other editors, but 58ms seems really slow - definitely not "next display refresh". All…
The good-ish news is that as the frame rate goes up, compositor latency goes down, as it's usually an integer multiple of frame refresh time.
I'm also interested in influencing the design of next gen systems to reduce compositor latency, but I'm apparently pretty much alone in that interest.
Re: Zed, a collaborative code editor, is now open source
#183Re: Zed, a collaborative code editor, is now open source
#184Re: Zed, a collaborative code editor, is now open source
#185Any pictures of how Zed actually looks? Searched their site and couldn't find any...
Re: Zed, a collaborative code editor, is now open source
#186Earlier quoted context omitted.
Is there any way to make it compatible with macOS 10.14? Your minimum macOS requirement is literally just one release away from what I have!
I'm running it just fine on 10.14.
Did you have to build it from source?
Re: Zed, a collaborative code editor, is now open source
#187> respond to your keystrokes on the next display refresh Claimed insertion latency for a keystroke: - zed 58ms - subl 75ms - vscode 97ms - clion 83ms 60 Hz displays refresh once every ~16.6ms. 58ms to insert a character is ~3.5 frames. My laptop can do 120 Hz, and other monitors can even do 300 Hz. Yeah, it's a lot faster than the other editors, but 58ms seems really slow - definitely not "next display refresh". All…
As computers got more complex, latency increased. It's really pretty remarkable to see how things have changed over the years[1]. I do agree that 58ms seems far outside of the range of "next display refresh", however. [1] https://danluu.com/input-lag/
Wow, the numbers are entirely unexpected. I want to see the latency when you have no display server, having booted directly to a shell.
I imagine modern competitive twitch-reflex videogames (fps, fighting) must have far less input latency - 100ms must be totally unacceptable. Suppose that's the power of a GPU.
Re: Zed, a collaborative code editor, is now open source
#188Re: Zed, a collaborative code editor, is now open source
#189How many people find real time sharing helpful? I've never found it to be beneficial. I'm curious.
As a senior engineer, it really helps when helping junior engineers. When I'm on a call and we're sharing screens it gets really annoying having to tell them "no, go up. Go up, all the way up, the button at the top. THE TOP"
Having real time collaboration that works so seamlessly as Zed apparently does would really get me to consider switching IDEs!