agreed! I was not a huge fan of the AI integration before in Zed and would always switch to Cursor (or, lately Claude Code) to actually get something done. Now that Zed can target specific pieces of code from the sidebar and edit them directly, it's been my goto for the last 24 hours. I've yet to "eject" to my old tools.
I'd say it's closer to Claude Code than to either of the two IDE-oriented ones. I say this because it actually does the right thing more often than either Cursor or Windsurf. It gathers the right context, asks for feedback when needed and has yet to "go back and forth between two failing solutions" like I've seen Cursor do.
I don't know what Zed's doing under the hood but the diffing tool has yet to fail on me (compared to multiple times per conversation in Cursor). Compared to previous Zed AI iterations, this one edits files much more willingly and clearly communicates what it's editing. It's also faster than Claude Code at getting up to speed on context and much faster than Cursor or Windsurf.
Reading an audiobook is reading. As a partially blind person, it is the only way I can read comfortably. I'm not sure how a different word would help. If one was reviewing the audiobook, specifically, they might call it out in order to comment on the narration quality, etc. But if you listened to the book, you've read it.
I don’t agree. Your eyes sending signals to your brain is different than your ears. It is a different way to digest information. People tend to remember 20% of what they hear and only 10% of what they read. While the hearing is greater it doesn’t include the same process of acquiring information. “Listening is reading” is a false generalization just because you were able to gather the same information doesn’t mean you “read” the book. I don’t consider a person in a wheel chair a “walker” but I would go for a “stroll” (roaming) with them.
It's always been my assumption that we wash our hands when we go to the bathroom for two reasons:
1. Wiping your butt can lead to feces getting in your hand. A lot of diseases can come from feces.
2. It's a good frequency to wash off whatever else you've been touching that day.
Assuming you go to the bathroom 3-7 times a day, that's that many opportunities to wash off the dirt you were digging in, trash you picked up off the street or someone else's hand you shook.
For those thinking any technology might be a "cure" for a specific disability, I highly recommend checking out the book Against Technoableism by Ashley Shew [1]. It really helps articulate the reasoning behind "nothing about us without us" in the context of "life changing" technology - including snakeoil bullshit like this.
In my experience, having to rebase on top of a branch with a lot of "lint" "quick fix" "let's try this" "oops, how about this" can be draining and sometimes lead to accidental code deletion.
I like squash merges because I know it was the author's intended change that I'm merging or rebasing onto.
I've worked in orgs that use long lived branches and short lived branches... And short lived branches are by far less stressful to deal with if you can do it, precisely because of merge conflicts.
Reality is never going to match your desire. Things are going to get messy, and so you end up with squashable commits among your commits that shouldn't be squashed. The branch you're merging should match your intent for atomic changes to the code that can be easily reasoned about when rebasing, merging, and bisecting.
You write to history once, but you read from it many times. Therefore, optimize for reads.
> In my experience, having to rebase on top of a branch with a lot of "lint" "quick fix" "let's try this" "oops, how about this" can be draining and sometimes lead to accidental code deletion.
" But this is not always possible, so one can use the rewriting history tools that were mentioned."
> I like squash merges because I know it was the author's intended change that I'm merging or rebasing onto.
This is really cool! One quick note about your marketing copy, though:
> Audio for humans, not robots
There are plenty of blind folks who use traditional text to speech for navigating our devices. We prefer the robot text at ridiculously high speeds. We're humans too.
I would love the option to switch to a more natural voice for more literary text (or even a fan fic) so I'll definitely be checking this out
> I would love the option to switch to a more natural voice for more literary text (or even a fan fic) so I'll definitely be checking this out
I'm curious if it would be possible to do some kind of analysis to determine the number of individual characters in the text who are speaking, and then assign an appropriate voice to each of the characters. So if you had something like descriptive language interspersed with a conversation between two characters, that you'd have three voices (a narrator, Character A, and Character B) that are consistent across the text.
For more complex writing with many characters, you'd probably need a wide library of possible voices, and the analysis piece would need to spot-on, since it would be very confusing to have one characters' lines spoken by the wrong voice.
Regarding fanfics, many authors give (or withhold) permissions around creating derivative versions of their work via avenues like ficbinding. Before using a tool like this to create an audio version of their writing, I'd suggest reaching out to a fic's author to see if they'd be okay with that. For personal-only use, though, and especially if it's in context of accessibility for visually-impaired folks, I imagine that many of them would probably be okay with it.
Thank you so much ; you've given me a lot to think about.
I'll admit I don't listen to a lot of fiction content, I prefer to watch it.
I do plan on adding additional voices and one brand of fiction I do like listening to is stories for adults. I used it on the Calm app to fall asleep before, and it is great for calming the mind.
For the time being the product is best for non-fiction, but I'll keep an eye on opportunities to make it work better for fiction.
Thank you also for opening my mind on how copy is perceived by blind users. It will be an honour to help them more. Empowering others through tech is why a lot of us work so hard. This is a great reminder.
