why would you develop such dependency on a proprietary piece of code?
> I'd even say, perhaps it's best not to tell people that their problems aren't problems to begin with. I'm not saying one should care, it'd be enough just not to explicitly dismiss on their face.
generally speaking, the opposite is true - people need to take some accountability for their problems, thanks to the disintegration of conversation people have had it too easy to simply mute or block opinions they found uncomfortable, helping them to avoid facing problems much more than it's sane to do
yep well, as far as I'm concerned they're all crap including SwiftKey esp. when compared with using a properly set-up computer
phones aren't great for input, and perhaps won't be in the foreseeable future, but using proprietary closed keyboards with no roughly-equivalent alternatives just compounds the problem
every time I want to type something substantial, in any language, I wait until I have access to a computer; it's particularly bad in Japanese and Chinese in my experience, but it's not great in any language - in Asian languages you'd get good over time with some specific system (say 4-corners, zhuyin, kana/conv, and specific predictive dictionaries) and then have support end, so why even bother?
Good reliable text to speak on mobile is quite seemless and pleasant. For instance to "type" messages or thoughts as you're biking. I used a proprietary offline one from Vivo and it was great (unfortunately the keyboard had other issues)
I'm not a native speaker but Microsoft's pinyin on windows and Google's pinyin input system on Linux both give much better results than the few open source alternatives I've tried .. so the situation is only marginally better at the desktop (I haven't tried text to speak on the desktop)
It's one of those weird areas where theyre both supposedly old solved problems - but for some reason nobody has bothered to make open source solutions
it may sound overkill, but I mostly use my own personal modifications to ibus-typing-booster for my input (formerly to ibus directly)
it works well enough for me on my computer, and i simply avoid phones for input - anything "phone" is factory-lobotomised and nothing else should really be expected, and even if the software were to suddenly be best effort, you'd still have to overcome very taxing interface limitations
this has the disadvantage of making you even less at home in other devices but hey, my reality is what when this happens I wouldn't have been any better off regardless
Yeah, those are yaks I'm not ready to shave. And I do mostly stick to voice messages on the go. But some people are allergic, so I do try to use voice-to-text then. I'm pretty sure the Ubuntu package for input method googlepinyin is entirely offline so I'm not too concerned. More just disappointed with how far behind opensource options are - when these things have been around for a decade+ and are described in textbook by this point
> I'd even say, perhaps it's best not to tell people that their problems aren't problems to begin with. I'm not saying one should care, it'd be enough just not to explicitly dismiss on their face.
generally speaking, the opposite is true - people need to take some accountability for their problems, thanks to the disintegration of conversation people have had it too easy to simply mute or block opinions they found uncomfortable, helping them to avoid facing problems much more than it's sane to do