From: Jason Stewart Date: 2009-09-03T21:34:28+09:00 Subject: Re: Simple New Ruby Programmer Problem with $stdin.gets On Wed, Sep 2, 2009 at 7:05 PM, Mason Kelsey wrote: > Sorry for the typo; I didn't mean "monitor".  I'm a retired programmer, a > Dilbert dinosaur, and certainly know that inputs don't come from monitors. > The first computer I worked on had vacuum tubes and 1K of mainframe memory! > Having been in the field for 36 years before my retirement in 2001, the term > terminal used to be used in the distant past for a monitor/keyboard combo or > a teletype machine, typically with acoustic phone couples for the > connections to the mainframe.  Clearly that is not how some use the term > terminal any more.  So the world changes, what else is new? The more things change, the more they stay the same :) > I tried using the run/cmd that you suggested, and it does work.  Thank you. > But I assume most Ruby programmers don't work in the run/cmd environment, > what I call the DOS Box.  If so that is a serious step backwards by about 28 > years.  I actually had to use the "dir" and "cd" commands to get to the > subdirectory where my rb files were.  I haven't used them in so many years I > have forgotten how many have passed.  DOS commands, today!  What a > disappointment!  How primitive! Most "serious" ruby programmers that I know do not use a win32 environment. Mac or Linux seems to rule the Ruby world. While there is alot there to play with for windows people, *nix-like OSes will always rule when developing in languages like Ruby, Python, and Perl due to the ease of access to compilers and libraries like mysql, libxml, etc. In some respects, an IDE and file explorer/finder is a serious step backward in productivity. I'd rather have 3 terminals open tailing my log files, running tests, and one extra one to manage things than to have to deal with an IDE that may or may not provide a nice interface to these things. Scite is not a bad way to get started with ruby though. It was my first ruby editor. Regards, Jason