261–270 of 386 posts
Earlier quoted context omitted.
> you might be used to waiting 100 ms for a character you typed to appear. The latest benchmark I could find is 2022 and it's nowhere as bad as you claim https://github.com/microsoft/vscode/issues/161622#issuecomme...
I ran it on VS Code and kitty recently: https://news.ycombinator.com/item?id=45253927 https://news.ycombinator.com/item?id=45254054
Just wanted to mention that some basic Windows-OS keyboard shortcuts don't work, like ALT+F to open the File menu. Also things like ALT+SPACEBAR to bring up the system context menu for the focussed window (the menu with maximise, minimise, close options etc.) do not seem to work. I'm guessing with the DirectX rendering backend, the 'app' is rendered more akin to a video game than a native win32 process. Also after in…
I'm not sure what gave you that impression. I'd say Rust is pretty well known for fat binaries
Earlier quoted context omitted.
Zed is pretty awesome on macOS and Linux, but I tried the Windows version tonight and things that work great on the other OSes aren't working on Windows. I've noticed: - Issues with various keybinds not working as expected, e.g. Ctrl+S to save works on my Linux machines but not Windows if Vim Mode is enabled - Issues with LSPs/diagnostics not working on Windows the same way they work on macOS/Linux - The terminal hol…
> setting environment variables in the OS is easy Windows has a GUI, how can it not be easy. /s It isn't as easy as on Linux, but you press Windows, type env, click edit Variables then select User vs. System, the you press add. That's not too complicated.
Like, it’s not great.
Earlier quoted context omitted.
Strangely it's the actual binary's .text section that's about 400MB. Time to dive in!
Welcome to static linking of large applications. The world moved into dynamic linking in the 1980's for a reason. It is cool to advocate for a return to static linking when it is basic CLI tools.
Unfortunately, I tried to use zed as my daily driver, but the typescript experience was subpar. While the editor itself was snappy, LSP actions like "jump to declaration" were incredibly slow on our codebase compared to VS Code / Cursor.
That doesn't make sense, they both use tsserver under the hood.
One thing I noticed in the implementation is that it looks like it is using stdin/stdout for the JSONRPC inter-process communication, rather than named pipes or sockets. VSCode uses named pipes. I wouldn't be at all surprised if that's a significant bottleneck - I'm about to file a bug.
EDIT - commented on the tsserver thread here: https://github.com/zed-industries/zed/issues/18698#issuecomm...
I've been using Zed primarily for months but I just switched back to VSCode for 2 reasons, one of which is kinda my fault and the other it's unclear where the fault is. 1. I deleted a few hours of work because I was late night coding and I decided to rename a file before check-in and delete the old version. Well I renamed it and Right-Click -> Deleted the new version by accident. It turns out Zed has both "Delete" an…
So --
* if there is no such dialog, it's on zed * If there is such a dialog and you clicked yes, it's on you
[Window Title] Critical [Main Instruction] Unsupported GPU [Content] Zed uses DirectX for rendering and requires a compatible GPU. Currently you are using a software emulated GPU (Microsoft Basic Render Driver) which will result in awful performance. For troubleshooting see: https://zed.dev/docs/windows Set ZED_ALLOW_EMULATED_GPU=1 env var to permanently override. [Skip] [Troubleshoot and Quit] Ah bummer.
That's more of an issue with your system than an issue with Zed, you have to veer pretty far from the beaten path to not have proper DirectX nowadays. Are you running Windows in a VM?
It may not be an actual problem with zed either, despite the warning.
Earlier quoted context omitted.
You literally can’t tell the difference in a 20ms delay. That is an order of magnitude lower than the neural feedback loop latency. You may think that you can, but studies don’t back this up.
"Order of magnitude", so you're saying the neural feedback loop latency is >100ms? That seems obviously wrong. Also you can absolutely feel the visual difference between 60Hz (~16ms) and 120Hz (~8ms), and for audio it's even more nuanced. Just because studies don't back this up yet doesn't make it false. I imagine this is really hard to measure accurately, and focusing only on neuron activity seems misguided too. Our…
Human neural feedback loop latency is a range that varies widely depending on the type of loop involved. Reflex loops are fastest, operating in tens of milliseconds, while complex loops involving conscious thought can take hundreds of milliseconds.
Short-latency reflex: 20-30ms. Signal travels through spinal cord, bypassing the brain. E.g. knee-jerk reflex.
Long-latency reflex: 50-100ms. Signal travels to the brainstem and cortex for processing before returning. E.g. Adjusting grip strength when an object begins to slip from your hand.
Simple sensorimotor reaction: 230 - 330ms. Simple stimulus-response pathway involving conscious processing, but minimal decision-making. E.g. pressing a button as soon as light turns on.
Visuomotor control: ~150ms, adaptable with training. Complex, conscious loops involving vision, processing in the cortex, and motor commands. E.g. steering a bike to stay on a path in a video game.
Complex cognitive loops: Brain's processing speed for conscious thought is estimated at 10 bits per second, much slower than the speed of sensory data. High-level thought, decision-making, internal mental feedback. E.g. complex tasks like analyzing a chess board or making a strategic decision.
Earlier quoted context omitted.
> Not to mention it takes minutes for the window of Zed to open, whereas VSCode is almost instant. That one is interesting. It's much quicker for me, even cold starts are below 1s, and subsequent startups are basically instant.
Cold starts are minutes, subsequent startups are much faster than VSCode[1]. I wonder why though. [1] I have not measured subsequent launches of VSCode though, but Zed is relatively pretty quick after the initial launch.
Earlier quoted context omitted.
> you might be used to waiting 100 ms for a character you typed to appear. The latest benchmark I could find is 2022 and it's nowhere as bad as you claim https://github.com/microsoft/vscode/issues/161622#issuecomme...
I ran it on VS Code and kitty recently: https://news.ycombinator.com/item?id=45253927 https://news.ycombinator.com/item?id=45254054
I know as a matter of fact that bad extensions slow down VSCode significantly.