[ej_campbell]

Seriously? Typing on glass without auto-correct is painful. Do you really think it was a bad idea for designers to design that feature?

[yorwba]

I type on glass without autocorrect. I use that bar of predictions above the keyboard, which occasionally suggests words that slightly differ from what I typed, and if I made a typo, I'll gladly accept the correction. But I'd never use a "feature" that changes what I typed after I already moved on to the next word. I wouldn't call it painful, but maybe I'm unusually good at hitting the intended key most of the time.

[andrewaylett]

Google's keyboard recently added the ability to auto-correct a word back, which I find really useful when I'm using swipe typing -- usually I'll fix as I go anyway, but I'm not infallible and if I expected a swipe to give me the right word, I might not otherwise notice until I go back to proof-read before hitting send.

[pg_bot]

Yes. The computer should never do something that I haven't explicitly told it to do. You can design the same exact feature but I need to trigger it, the machine should not be making decisions for me.

[ej_campbell]

> When designing anything, if you think that you are doing someone a favor by doing work ahead of time please stop.

And you think that is the right call for the majority of people?

[Fnoord]

I use SwiftKey (without cloud predictions) and if you press spacebar that's the equivalent of "explicitly telling it". The thing is that usually, the auto correct is correct so when you see it is not you click on the word you (according to the computer) "made up", et voila.