Earlier quoted context omitted.
> "Order of magnitude", so you're saying the neural feedback loop latency is >100ms? That seems obviously wrong. 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 spin…
A few years ago I did some testing with a quick Arduino-based setup I cobbled together and got some interesting results. The first test was the simple one-light-one-button test. I found that I had reaction time somewhere in the 220-270ms range. Pretty much what you'd expect. The second test was a sound reaction test: it makes a noise, and I press the button. I don't remember the exact times, but my reaction times for…
Zed is now available on Windows
371–380 of 386 posts
Re: Zed is now available on Windows
#372Re: Zed is now available on Windows
#373Earlier quoted context omitted.
I just compiled "zed" with "cargo build --release" and not only did it pull >2000 dependencies, its size (executable file) is literally 1.4G. Debug is 1.2G. $ pwd /tmp/zed/target/release $ ls -lh ./zed -rwx------ 2 john john 1.4G Aug 28 17:10 zed --- $ dut zed/ | sort -h 598M 0B | | /- webrtc-sys-0a11149cbc74bc90 598M 0B | | | /- out 598M 0B | | |- webrtc-sys-090125d01b76a5e8 635M 160M | | /- s-hal7osjfce-1h7vhjb-4bd…
Cargo does the de-duplication, but only up to a point. If two packages request the same dependency with semver ranges that have a common overlap (say, `1.4` and `1.6`) then it will use a single package for both (say, `1.7.12`). But if they request semver-incompatible versions (`2.1` and `1.6`) then cargo will use both.
Re: Zed is now available on Windows
#374Zed looks and feels amazing to use. I test-drove it for a bit on my linux system, and the feel of it is difficult to convey to those who have not tried it yet. It's easy to overlook the significance of gpu accelerated editor - but I promise you, use it for a bit and you'll be sold. The only feature that is preventing me from switching to Zed is the current lack of DevContainer support[1]. After investing a significan…
I agree from a company perspective using dev containers gets all devs on the same page
Re: Zed is now available on Windows
#375Earlier quoted context omitted.
yeah I just tried the windows build and they are indeed behind a confirmation box (for both trash and delete). That's not the impression I got this morning from reading OP's comment
OP here. I have muscle memory from many years of using VSCode before Zed. "Delete" is the last option in the right click menu for both and when you select it both show a very similar dialogue box asking you to confirm. VSCode's 'Delete' by default moves the file to the trash and can be undone with Ctrl + Z. Zed's 'Delete' skips the trash and can't be undone with Ctrl + Z. I should have mentioned the confirmation box…
Re: Zed is now available on Windows
#376Re: Zed is now available on Windows
#377Earlier quoted context omitted.
> Storage is cheap I'll be very grateful if you stopped using all my RAM for two buttons and a scrollbar thank you.
OSes don't load the full executable into physical RAM, only the pages in the working set. Most of the Zed executable's size is tree-sitter code for all the supported languages, and only needs to page in if those languages are being used in a project.
Re: Zed is now available on Windows
#378Tested it a bit on a 2000 LOC python file, autocomplete is sluggish compared to VSCode (VSCode completes almost instantly but Zed waits about half a second before doing so). I didn't configure anything so I'm a bit disappointed...
Zed's ootb Python experience is poor since they use pyright as the LSP. There's threads on the issue tracker about replacing it, maybe check back in six months.
Re: Zed is now available on Windows
#379Re: Zed is now available on Windows
#380Earlier quoted context omitted.
One of the reasons why I'm not fully switching yet is a Zed's inability to update the currently open file with changes made elsewhere [1]. All the other editors I use are aware of outside changes, but not Zed. And I'm just not willing to close and reopen the file to get fresh contents. Eventually, I'll forget to do it and lose some work. [1] https://github.com/zed-industries/zed/issues/15791
How do other editors handle this in your experience? I’m pretty sure VSCode behaves exactly the same, with the addition of a manual “merge” editor when you try to save, but never shows changes live for a modified file. Changes to open files without any modifications in the buffer are always shown. Are you using any kind of containers or virtual fs that might be interfering?