My solution - not fully executed yet, though - to this problem is to have multiple monitors, keyboards and trackballs in my working room at home. The primary place I'd work at is a standing desk, with keyboard, trackball, monitor perfectly set up for this purpose. Beside these, there is another monitor, another keyboard, and another trackball, at a lower level, set up for when I'm sitting. The screen is mirrored on both.
I can walk around if I want to, because I have screens on the side too - though not input devices. I'm ok with inputting in two possible locations. But it is useful to be able to turn around, stare out the window, then look aside, and see my screen.
There is also the TV in the living room, when I go out and explain stuff to my wife (rubber duck programming is awesome). There, I use a laser pointer to point at specific parts of the screen. If I wanted to, I could have a small device, like the raspberry pi in that room, with other input devices attached, if I'd need to do anything there. The raspberry would just proxy the input events to my main computer over the LAN (there are N number of solutions on how this can be easily done).
I tried experimenting with other ways of working with a computer, such as speech recognition, but found that to be lacking at this time. Takes far too much time to set up, and the reliability is low. I'm also playing with Stenography, where I press chords to input text, instead of typing it out by the letter: this drastically reduces hand movement, and increases your speed, but the learning curve is steep, and takes a looong time. And it still requires a keyboard. Or a piano. A piano may even be better, dunno, didn't try that yet.
Yeah, I've thought about a stenograph, but swapping one keyboard for another doesn't really set me free... and I want to be free, damn it, free! :'(
Well, one can install Ubuntu over Android, and/or (gasp!) use a Windows phone to do all of their important computations. Technically speaking the keypad on our phones are the most ergonomic keyboards on the planet--we only have to use our thumbs. When we type on a phone keypad our wrists are in a much better position for future non-keyboard wrist related activities. I think that's one of the main reasons as to why there are more phone users than computer users.
Solution! Buy an Octacore ARM based phablet. If you really need a number cruncher skip past the Nvidia Shield, and make a tablet out of the Nvidia Jetson TX1 (256 cuda cores baby!) ;D
You haven't heard of texting thumbs, have you?
Well, one can install Ubuntu over Android, and/or (gasp!) use a Windows phone to do all of their important computations. Technically speaking the keypad on our phones are the most ergonomic keyboards on the planet--we only have to use our thumbs. When we type on a phone keypad our wrists are in a much better position for future non-keyboard wrist related activities. I think that's one of the main reasons as to why there are more phone users than computer users.
Solution! Buy an Octacore ARM based phablet. If you really need a number cruncher skip past the Nvidia Shield, and make a tablet out of the Nvidia Jetson TX1 (256 cuda cores baby!) ;DYou haven't heard of texting thumbs, have you?
I was going to reply with something similar, especially when you see threads about over worked thumbs (https://geekhack.org/index.php?topic=83157.0)
Because of the keyboard we need a desk to put it on.
Show Image(http://www.unlimitedpriorities.com/wp-content/uploads/speaknow.jpg)
Show Image(http://www.unlimitedpriorities.com/wp-content/uploads/speaknow.jpg)
Show Image(http://www.unlimitedpriorities.com/wp-content/uploads/speaknow.jpg)
How well do you think that works with:
#include <stdio.h>
#include <stdlib.h>
int main(int argc, const char *argv[])
{
printf("Hello %s, can you convert me to code?", "Google");
return EXIT_SUCCESS;
}
^-^
This fellow has a pretty elaborate system:
This fellow has a pretty elaborate system:
Yeah, I've seen this before, but I'm not convinced. I imagine it takes ages to teach the computer what your beatboxing means and I bet it's a pain to add new stuff to it. This, and speech recognition in general, could never work in an open office. And no doubt there will eventually be complaints about saw throats! :D
This fellow has a pretty elaborate system:
Yeah, I've seen this before, but I'm not convinced. I imagine it takes ages to teach the computer what your beatboxing means and I bet it's a pain to add new stuff to it. This, and speech recognition in general, could never work in an open office. And no doubt there will eventually be complaints about saw throats! :D
It's not that bad. It took me about a week to set up the basics, and once you're there, adding new stuff is the easy part. Remembering all your **** is the harder one. But yeah, not an option in an open office :)
Show Image(http://www.unlimitedpriorities.com/wp-content/uploads/speaknow.jpg)
How well do you think that works with:
#include <stdio.h>
#include <stdlib.h>
int main(int argc, const char *argv[])
{
printf("Hello %s, can you convert me to code?", "Google");
return EXIT_SUCCESS;
}
^-^
It works reasonably well - as in, usable, if you spend enough time to set your environment up to work in such a system. I used to use voice recognition a few years ago, when I was told not to use my hands to type, until they heal, and while the speed was slow, and it was annoying, I could get stuff done I wouldn't have been able to otherwise. So, surprisingly, it can work. But takes a lot of effort, and the comfort won't be nearly as good as with a good keyboard.
I'm guessing you do 'verbal shortcuts' e.g. 'standard library' maps to #include <stdlib.h> and similar, or ??