12.01.2013 Views

The Rainbow Vol. 09 No. 01 - August 1989 - TRS-80 Color ...

The Rainbow Vol. 09 No. 01 - August 1989 - TRS-80 Color ...

The Rainbow Vol. 09 No. 01 - August 1989 - TRS-80 Color ...

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

I Print#-2,<br />

10 THE RAINBOW <strong>August</strong> <strong>1989</strong><br />

Eight Years Strong<br />

B<br />

y now, most of you have had a month to pe ru se o ur Eig hth Anni versary Issue last<br />

month and. for long-time reade rs ofT HE RA INBOW, I know some of you wondered<br />

why my column did not mentio n anything about it. W e ll , the truth is that I was<br />

simply confused abo ut the month for whi ch 1 was writing, thinking the column th at ended<br />

up in 1 ul y's issue was for the 1 une issue . Of course, you reall y don ' t need me te lling you<br />

th at the anni versary is upon a ll of us because it says so o n the cover.<br />

As is done every year. the anni versary issue features a surprise. This year it 's a booklet<br />

of O ne-Liners. (Incidenta ll y. if you mi ssed last month's issue , you can still get the bookl et<br />

from us.) I tho ught the booklet was an appropri ate way to celebrate an anni versary (whic h.<br />

except fo r Br te, may make us the longest continuously-published compute r magazine in<br />

the worl d).<br />

I have always been exceptiona ll y partial to One-Liners, pe rh aps, because they hark<br />

back to the earl y days of the <strong>Color</strong> Computer. when the CoCo came w ith an astonishing<br />

4K of mem ory. By the time the system overhead was accounted fo r. the re was abo ut 2K<br />

fo r program writing. I admit th at 2K is quite a bit mo re th an the average O ne-Line r (or<br />

T wo-Line r), but th e bi g deal in those days was fittin g a usable program in to the avail able<br />

me mo ry.<br />

<strong>No</strong>pe. those 2K spreadsheet programs were not as fancy as the program s we have<br />

today, but l think if you asked anyone to wri te a program th at would do something '" major"<br />

I ike spreadsheetin g, word processing, data communications or the li ke, and required it to<br />

fit in 2K. you would be laughed out of the door. But it was do ne .<br />

When T HE RA INBOW first started , one of the most-often asked questions was wheth er<br />

the owne r's CoCo was working ri ght because the screen sho wed abo ut 2K memory<br />

avail able and the "salesman to ld me it was a 4K machine." That questi on, o f course, was<br />

repeated when Tandy came o ut w ith the "amazin g'' 16K upg rade and the memory<br />

avai I able was some 14K.<br />

Indeed , I remem ber the clay whe n m y local salesman call ed me to say the 16K upgrade<br />

was in , if I wanted it. I sped home, got my CoCo, and sped over to Rad io Shack on my<br />

lunch hour to have a "full -bl own"<strong>Color</strong> Computer. <strong>The</strong> two days ittook to have it in sta ll ed<br />

were among the longest of my I ife!<br />

T he interesting thing is th at I never ran out of mem o ry when I had the 4K CoCo, but<br />

I di d when I got the 16K upgrade . I am sure I simply was m ore careful about w hat I was<br />

writing o n the " little machine ," and fi g ured th e sky was the limit w ith the " bi gger" one.<br />

Of course. I knew a I ittle more about programming by the ti me the upgrade was avai I abl e.<br />

Some earlie r iss ues of T HE RA INBOW had a few interesting debates abo ut programming<br />

structures. But one of the most inte resting debates was the one th at went on in my own<br />

office- whether to com press code in li stings or run it so th at it was easie r to read.<br />

We fin a ll y decided we woul d use the easy-to-read fo rmat for o ur BASIC li sti ngs.<br />

although th at meant we had to reject one o r two programs. In orde r to s imply get them to<br />

fit into the CoCo's memory, the authors would pack the li stings, e liminatin g the spaces<br />

between keywords.<br />

We tho ught an importa nt part of o ur job was to teach o ur reade rs a li ttl e something<br />

about how programs worked, and if it was hard (or, sometimes, a lm ost impossibl e) to read<br />

them . it woul d be diffi cult at best to f ig ure o ut the logic of what the w rite r was try ing to<br />

do. W e have kept that gene t·al philosophy up to the present day.<br />

<strong>The</strong> exception to th at rul e. o f course, is o ur One-Liners (and Two-Line rs). But each is<br />

an exercise in programming skill s, and it reall y isn't hard to fo ll ow a sing le line's logic.<br />

A nd, too. they do remind us o f o ur earl y days with CoCo, where every byte was precio us.<br />

- Lonnie Fa lk

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!