Hey, that seems really cool, has anybody tried using one of these? I mean how well does it work in practice and how fast can one type?
Just curious as to whether anyone else thinks Dasher + Matchbox in a little pda thingy would rock.
Since most PDAs are used as notebooks as well, being able to write quickly would be very welcome. If it's significantly faster than other methods (recognition of handwriting, the systems used on cellphones) then, yes, absolutely it would rock.
What do you mean by this? 64Kbits is worthless for listening to any music I own while 128 is good enough to not actually annoy me much of the time so why should I be interested in these tests?
I suppose he meant that since at 128Kbps all codecs perform quite well. Therefore personal preferences affect the results too much, i.e. some people like bass boosts and lots of treble, although this is not accurate in the sense that it differs from the original recorded signal.
If 128kbps is 'good enough' for you then I too suppose you would fall into the sounding 'good' instead of sounding 'accurate' category.
Well, yes good design certainly helps, but if the code is rubbish the design won't get you very far. Most people would like it to be the way you described, however it is a well established fact that testing is currently a necessary part of building reliable software.
Webapplicaions in their current form are not only limited by the bandwidth available, but also by the web-model of loading pages. Every time you click a button in the application your browser has to fetch and render a complete page, even though only a few lines on the page may have changed. This severely limits the interaction that can be provided. You could of course get around this by using JavaScript or Flash or whatever, but all those techniques integrate poorly with the server-sided part of the application.
Slashdot Mirror
Negative, private
Those you mention are known to hit South America, and this one is going for the northern hemisphere.
Either way, nothing the mobile infantry can't solve
Hey, that seems really cool, has anybody tried using one of these? I mean how well does it work in practice and how fast can one type?
Just curious as to whether anyone else thinks Dasher + Matchbox in a little pda thingy would rock.
Since most PDAs are used as notebooks as well, being able to write quickly would be very welcome. If it's significantly faster than other methods (recognition of handwriting, the systems used on cellphones) then, yes, absolutely it would rock.
What do you mean by this? 64Kbits is worthless for listening to any music I own while 128 is good enough to not actually annoy me much of the time so why should I be interested in these tests?
I suppose he meant that since at 128Kbps all codecs perform quite well. Therefore personal preferences affect the results too much, i.e. some people like bass boosts and lots of treble, although this is not accurate in the sense that it differs from the original recorded signal.
If 128kbps is 'good enough' for you then I too suppose you would fall into the sounding 'good' instead of sounding 'accurate' category.
Well, yes good design certainly helps, but if the code is rubbish the design won't get you very far. Most people would like it to be the way you described, however it is a well established fact that testing is currently a necessary part of building reliable software.
Webapplicaions in their current form are not only limited by the bandwidth available, but also by the web-model of loading pages. Every time you click a button in the application your browser has to fetch and render a complete page, even though only a few lines on the page may have changed. This severely limits the interaction that can be provided. You could of course get around this by using JavaScript or Flash or whatever, but all those techniques integrate poorly with the server-sided part of the application.