python was 2919

Sorry, I had to delete all those f***ing colons.

order

It may be a measure of something happening...but I'm not sure what. This is one of those times that being too close to the birth of stuff is a hindrance to objectivity. (Shut up, Mark.)

Note that "stays in core" was a very important part of that sentence. What didn't get used in some olden days, was put out to pasture on the disk, until somebody needed the code. JMF "threw out" tons of instructions once he was done with using only what's needed. One of AOL's bad programming habits is the insistence of having every piece of code I might use in place and in core before any data spaces were used. This caused most^Wall of my BSODs.

One of these days, the biz will rediscover that a computer is no good to anybody unless it has lots of room for data.

I don't. That was part of the user thruput (for Mark's erudition, throughput) problem.

Have you read the book about Boyd yet? This is exactly what Lynn is talking whenever he mentions the guy. There is an underlying something..rule, law, metric.. about sorting out when and how to make a decision. There is a hump when just doing it is the most efficient rather than elaborate sifting schemes for being "fair". This has to do with all kinds of meting(sp?) out resources. Any kind of resource.

Yes, it would explain that one, too. PDP-10s were work horses. You can't expect a workhorse to prizes at the Lipannzer(sp?) show. replaced

Yes! You can't imagine how pleased I was when you wrote about that. He is headed in the "right" direction. Time will tell how well this atbreastude spreads and survives. I worry about this one a lot.

Even that isn't an excuse for the crap and design^Wdistribution decisions that have been made. People can live with this kind of constraint as long as they don't have work session interruptions. OTOH, the non-people computing cannot live with this.

BAH