Cursor is effective at making 90-95% of code changes, my only input being phrases like:
"change <foo> to work like <bar>"
"add an argument in <foo> to do <blah>"
"add assertions in <foo> that make sense"
("that make sense" isn't an abbreviation)
My physical contact during these operations is typically clicking files to open, highlighting text, accepting or rejecting changes, and making manual edits whenever I get frustrated with trying to explain things to the AI.
This is a big change over how I wrote code 5 years ago. It also seems like a temporary workflow that's bound to change.
This market resolves YES if at the end of 2025, I no longer physically touch my computer while editing code and instead only use spoken natural language.
I won't bet.
1,000
3.00@parhizj do you mean this?
This seems much slower and less precise than a mouse or track pad would be. But I haven't tried it myself.
@singer It's also available in linux. Unfortunately the amount of customization necessary for power users isn't truly readily available since they are kernel level drivers. Some years ago I used to use a gaming mouse for all cases. If you exclude gaming, you don't need one once you get used to mouse keys. As for precision, you can move the mouse up to one pixel at a time, so keyboard is definitely more precise. As for speed, I think once you learn how to use it (including acceleration modifier) you'll find it roughly on par or faster.
I never got around to writing my own mouse-keyboard software because it was always "good enough", but I can imagine that if I do it would be faster than a mouse.
@AriZerner You can interpret the market as being about whether I do it or not (it's already in fact technically possible today, just impractical). Sorry for the ambiguity.