vaskozl said:It is far easier to type on colemak than it is on qwerty. Simple obesrvations (F, J, semicolon) show that qwerty's design hasn't been built around much logic.
I swiched my little brothers layout to colemak when he was learning to type on the computer (he is now 11 years old). He is able to type (touchtype) much faster than anyone else in his class including his teacher. This goes to show that a fresh start with colemak, even if harder, yields much better performance that with qwerty.
As for steno... I would never switch to it. I can't type my name or nickname, nor that of my best friend. I want to be able to type in a number of languages with different symbols all in the same sentance without a headache. I want to be able to type out url's, mispell words on purpose and type 1337. I want to be able to use random slang I pickup from the internet without having to bother entering them into a dictionary. I wan't to be able to use my layout without having to download a shit ton of libraries on a computer. Steno sucks for me.
I agree, but as for speed, I still don't think that it can necessarily be traced back the layout alone. In a general sense, I don't think that the layout is the most important factor for speed.
I think you're looking at in the wrong way. I'm not going to switch to steno; I plan on adding it to my skill set. Most of the typing I do doesn't involve names or symbols, and plover allows you to add chords on the fly, so it would take just a few seconds to add names to your dictionary. Just because you learn steno doesn't mean you would have to use it for everything. I only plan on using it for writing in English. For example, I would write this post with steno. I wouldn't use it for symbols. Typing out full urls is inefficient in the first place, but I wouldn't use steno for browsing either.
If you wanted to write in 1337, you could just switch out of plover. Plover admittedly provides a horrible interface for turning it on and off without the use of the mouse. However, I've got around this by setting up a keybinding with sxhdk to start plover running or kill it. I haven't tested how quickly this works, but I suspect it would work okay. Potentially, you could set up a binding to use xdotool to interact with the plover window instead to turn it on and off. This would make it very easy to alternate between the two.
I think steno is a terrible way of doing anything like window management or most programming, but I think if used just for text input like it was designed for, then it can be useful.
Also, my point wasn't that we should all switched to steno; it was that if we all cared only about speed we would.
vaskozl said:Plus if you use the shell for any considerable amount of time you will find yourself typing things like:
optirun fgfs --generic=socket,out,20,127.0.0.1,34200,udp,../Aircraft/c172p/Panels/FGPanel_Protocol_c172p
How easy would it be to type this command out in steno?
O.o I spent about 8 hours in the terminal yesterday and do frequently use the shell, but I've never had to type something like that. This could just be because what I do differs from you or other people, but wouldn't you just alias something that long? Steno would be mostly useless for the terminal anyway, since I alias anything I use more than once to a short command. The solution would be to just not use steno for typing something like that.