The streaming dictation they also added in that release is also much appreciated although occasionally buggy.
1,664 karma · joined September 29, 2010
The streaming dictation they also added in that release is also much appreciated although occasionally buggy.
It's also larger, more satisfying tactile/clicky, and concave compared to the old button (which was rounded into the outside curve, not particularly be satisfying to press). I think the old one being so small and indistinct feeling, and also being so close to the cables meant you would never try to reach for it blindly. You do have to lift it up a bit, but the device is so light you can do that with the same finger you're using to push the button (of course you need another finger to push the top of the mini _down_).
I think neither old nor new button were really meant to be used more than occasionally, since you typically wake your Mac from the keyboard, and both designs reflect that. I do sympathize that the new version could be less flexible in different mounting positions though.
(that said, I'd bet Jobs/Ive Apple would never have shipped this, unless the height underneath was exactly perfect for even the larger fingers to fit)
I agree it's tricky to find the balance of a truly blind playthrough, sans hints, and one that's also enjoyable to watch because the inferences are made reasonably quickly.
For those who don't know what happened next, and why Dragon seem to stagnant so much in the aughts, the story about how Goldman Sachs helped them sell to essentially Belgian Enron, months before they collapsed, was quite illuminating to me, and sad.
https://jvns.ca/blog/2024/01/05/do-we-think-of-git-commits-a...
I guess while it's true the storage layer is snapshot based, as you say, that only gets you so far conceptually, and it's probably best to focus on the _operation_ you're doing, as rebase, cherry-pick, apply-patch, etc are easier to think in terms of diffs.
When I used to use Phabricator, the fact that I could always fall back to handing it a raw patch file to submit changes also made it easier to reason about (regardless of what the server and client were actually doing).
Wouldn't be the first time. My previous Dell monitor, the U3818DW, had a bug with its USB-C implementation that only affected Macs (somebody proved via protocol inspection that they were actually implementing part of the protocol wrong; it just didn't manifest on Windows). Their support forums for the issue are full of a single Dell representative whose sole response was to remind all of the Apple users that _technically_, Dell never qualified this monitor for macOS, and it's their fault for not carefully reading the technical documentation before purchasing. (Naturally, many of the reviews on Amazon are of people plugging it into a MacBook Pro.)
Really soured me on the idea of buying a Dell monitor for anything Apple related after that.
Talon itself provides noise and speech recognition, and provides the framework that allows you to build automations with any program; Cursorless really helps make programming by voice feel comparable to typing.
For me, it's a combination of introducing alternate input methods (largely voice, but noises are also very additive -- they very well for fast/discreet actions, whereas voice is higher bandwidth but lower latency), as well as building higher-level and better integrations with applications. But I still have always to go personally.
I've been meaning to write up a blog post with everything that I've learned, but you know how it is :)
(Background: I have RSI, so I've been developing some integrations between applications and Talon Voice (https://talonvoice.com/). AppleScript ends up being surprisingly valuable/fast/reliable for applications that support it. I also built an integration with iTerm2's Python API before noticing that everything I was trying to do was already supported by its AppleScript dictionary, and was faster. In Google Chrome, the "iterate through tabs and execute javascript in them" is very useful for automating Google Meet muting/unmuting.)
Nothing against this excellent project though; I'm a big fan of Omar's Twitter! And I suspect most here will appreciate the easier scriptability of the filesystem approach than dealing with the atrocious syntax of AppleScript.
But after discovering it and getting through the learning curve (and there is one, that's probably the biggest reason why more people don't use it), it's something I look forward to using for the rest of my life. Even as my wrists start to gradually recover, being able to use voice/noise/eye tracking in tandem to the keyboard, allowing you to use the best for each purpose, is just so much more productive (not to mention, cool! fun!) that I doubt I'll ever go back.