On Tue, Mar 17, 2009 at 13:55, Bob McConnell <r...@cbord.com> wrote: > From: Chas. Owens >> >> Perl doesn't start having problems with files until you start getting >> into areas that the OS has problems with those files. Your machine, >> however, may have problems if it does not have enough memory. I >> remember working on a production machine that only had eight megabytes >> of RAM (of course, that was in 1999). And I had to type uphill, both >> ways. > > Typing is always an uphill battle, no matter which way you are going. I > really wish someone would perfect the neural interface to eliminate that > bottle neck. I could also use a decent pre-causal response generator. I > don't need much, just 3-5 seconds before the event would be adequate. > But I've been looking for both for more than 20 years now, to no avail. snip
I really do not want to see what my mind would write without the physical guard of having to move my fingers (or at least having to send the signals to my fingers). And think of the equivalent to carpal tunnel for your brain. -- Chas. Owens wonkden.net The most important skill a programmer can have is the ability to read. -- To unsubscribe, e-mail: beginners-unsubscr...@perl.org For additional commands, e-mail: beginners-h...@perl.org http://learn.perl.org/
