Yeah, but what if some of use want to program 3d games and we don't personally actually run Windows. That might be kind of a setback, don't you think? And even some Windows developers might want a cross-platform option. Instead of, you know, being a dick to everyone that doesn't run Windows. I don't know what platform the original poster develops on, but since he seems to be into OSS, it seems just barely possible that a Windows only solution might be a dumb suggestion.
Exactly. Maybe gaming is an art and maybe it's not, but that's not actually what we're talking about. We're talking about the games, themselves. Personally, I fail to see how a medium that combines so many art forms (architecture, music, modeling, digital painting, and so on) can fail to be art. Some people may have a greater desire than I do to make "art" an exclusive category.
If you're on linux, try out cvoicecontrol. I just ran across it yesterday (thanks to this thread), and it seems to work pretty well. I've only just tested it, but setting it up is very simple and it seems accurate enough.
I think you may be confused. First of all, there are way more than 26 sounds in the English language. It's more like 49 individual consonants, vowels, and dipthongs, and many monosyllabic words can be constructed from those.
As far as I can tell, you're saying that words would need to be spelled out character by character so you'd have to talk really fast to be productive. Custom dictionaries would go a long way towards fixing that. The main issue would be whether a particular speech recognition solution integrates well with the shell and/or dev environment being used. It would be fairly simple, with any software, to get it to recognize shell commands like rm, cp, |, and grep when they were spoken as words. When coding, it would also be pretty simple to recognize common keywords and operators and output the proper text. I don't think there would be much trouble with speed until stuff like variable names began to come up. Even then, the big problem isn't that storing variable names for later spoken use would be hugely difficult to implement; it's just that (afaik) it hasn't been yet.
Assuming that most words could be recognized when spoken, you wouldn't need to speak at a higher WPM than you type at. Conversations happen at around 200 wpm (just over 3 words per second), according to Wikipedia, so speed wouldn't be much of an issue.
I think the biggest problem with speech as an input for techies is that the software itself has not yet been written. While there may be recognition software that can comprehend speech at normal speed and append its dictionary as it runs, there's none that I know of that has been set up to function in a technical environment. It may be as simple as putting the pieces together, but it would probably require a lot of hacking on your own. The second biggest problem would be wearing out your voice, although that's something you can work with.
I like the color scheme. I'm sick of the shiny blues and greens that all the other OSes and linux distros seem to favor. I find warm colors more relaxing. I don't actually use Ubuntu anymore, or even have much of a color scheme (thanks to the Ratpoison window manager), but Ubuntu's window decorations and widgets were definitely a high point when I was running it.
In any car, though, you cannot drive better than ABS. It is faster than you. Period. You people who claim you're faster than the computer are wrong.
It's not an issue of speed. It's about doing what's safest, which does not always equal what ABS does.
If you're referring to the fishapod, the real story wasn't that it was a "missing link". Discovering Tiktaalik provided insight into the conditions under which tetrapods evolved and made their way onto land.
It's not a theory because it's unproved. It will always be a theory. If we were to observe evolution occuring as it happened, then everything we saw would be a fact. We might explain those facts with the theory of evolution.
Yes. Linux distros, in their current state, force users to become administrators more often than I'd like. Obviously you have to do that to install software, but that should ideally involve nothing but a package manager.
I've found software that allows me to slow down a recording to be very helpful when I'm trying to learn music by ear. Audacity is the one I usually use, but there are many others.
Slashdot Mirror
Well, there might be a reason to if you could use one to boost performance with one.
Yeah, but what if some of use want to program 3d games and we don't personally actually run Windows. That might be kind of a setback, don't you think? And even some Windows developers might want a cross-platform option. Instead of, you know, being a dick to everyone that doesn't run Windows. I don't know what platform the original poster develops on, but since he seems to be into OSS, it seems just barely possible that a Windows only solution might be a dumb suggestion.
No.
(I find myself predisposed to one-word comments these days.
Yes.
Exactly. Maybe gaming is an art and maybe it's not, but that's not actually what we're talking about. We're talking about the games, themselves. Personally, I fail to see how a medium that combines so many art forms (architecture, music, modeling, digital painting, and so on) can fail to be art. Some people may have a greater desire than I do to make "art" an exclusive category.
By that same token, art is not just what the experts choose to recognize as art. Maybe art isn't a matter of "qualifying."
I agree. I'd like to do it myself (just because it's cool), but my schedule and mediocre programming skills may be a bit of a problem.
If you're on linux, try out cvoicecontrol. I just ran across it yesterday (thanks to this thread), and it seems to work pretty well. I've only just tested it, but setting it up is very simple and it seems accurate enough.
I think you may be confused. First of all, there are way more than 26 sounds in the English language. It's more like 49 individual consonants, vowels, and dipthongs, and many monosyllabic words can be constructed from those.
As far as I can tell, you're saying that words would need to be spelled out character by character so you'd have to talk really fast to be productive. Custom dictionaries would go a long way towards fixing that. The main issue would be whether a particular speech recognition solution integrates well with the shell and/or dev environment being used. It would be fairly simple, with any software, to get it to recognize shell commands like rm, cp, |, and grep when they were spoken as words. When coding, it would also be pretty simple to recognize common keywords and operators and output the proper text. I don't think there would be much trouble with speed until stuff like variable names began to come up. Even then, the big problem isn't that storing variable names for later spoken use would be hugely difficult to implement; it's just that (afaik) it hasn't been yet.
Assuming that most words could be recognized when spoken, you wouldn't need to speak at a higher WPM than you type at. Conversations happen at around 200 wpm (just over 3 words per second), according to Wikipedia, so speed wouldn't be much of an issue.
I think the biggest problem with speech as an input for techies is that the software itself has not yet been written. While there may be recognition software that can comprehend speech at normal speed and append its dictionary as it runs, there's none that I know of that has been set up to function in a technical environment. It may be as simple as putting the pieces together, but it would probably require a lot of hacking on your own. The second biggest problem would be wearing out your voice, although that's something you can work with.
I like the color scheme. I'm sick of the shiny blues and greens that all the other OSes and linux distros seem to favor. I find warm colors more relaxing. I don't actually use Ubuntu anymore, or even have much of a color scheme (thanks to the Ratpoison window manager), but Ubuntu's window decorations and widgets were definitely a high point when I was running it.
In any car, though, you cannot drive better than ABS. It is faster than you. Period. You people who claim you're faster than the computer are wrong. It's not an issue of speed. It's about doing what's safest, which does not always equal what ABS does.
If you're referring to the fishapod, the real story wasn't that it was a "missing link". Discovering Tiktaalik provided insight into the conditions under which tetrapods evolved and made their way onto land.
It's not a theory because it's unproved. It will always be a theory. If we were to observe evolution occuring as it happened, then everything we saw would be a fact. We might explain those facts with the theory of evolution.
How about taxes?
I don't think anything at all about gamers who haven't built their own systems. I'm just relating what I have experienced.
But that would still be the speed of light, wouldn't it? The fact that the speed of light happens to be slower there doesn't change that.
Yeah, but it will burn your cat hairless and knock him off his aircraft.
Hey, this is a nice place. Quit complaining!
Please tell me how a beam of light could possibly travel slower than itself.
I don't think I've ever met a gamer who hadn't built their own computer.
Yeah, gamers just love GNU/Linux. Did you even RTFH(eadline)?
Yes. Linux distros, in their current state, force users to become administrators more often than I'd like. Obviously you have to do that to install software, but that should ideally involve nothing but a package manager.
I've found software that allows me to slow down a recording to be very helpful when I'm trying to learn music by ear. Audacity is the one I usually use, but there are many others.
It's funny that even if you do mispronounce it like that, it comes out as "urine-us," which is just as bad.
I didn't mean /root, I meant the root directory, as in "/", and its subdirectories (aside from the user's home dir).