|
|
|
|
|
by MaDeuce
683 days ago
|
|
You're spot on. The IBM XT was introduced immediately after I graduated and went to work. My employer's employees got a 20% discount from IBM, as IBM was a client. I bought an XT (PC + 10MB hard drive) for $4K (list price $5K). A lot of money then for a new grad. The contrast between then and now is stunning. And software costs... this was also the era when every "application" (think accounting software: accounts payable, payroll, accounts receivable, word processing) was $495 per application. A small business could easily pay $2-5K for basic software to run their business. And then, of course, it was a nightmare to setup and use and almost impossible to pull off without a "consultant". But VisiCalc -- it was such a game changer. A totally different way of using a PC that enabled the "ordinary" non-computer person to become an order of magnitude more productive. I think Lotus 123 was the pinnacle of golden era of keyboard-driven spreadsheets, but it was only an incremental improvement over VisiCalc. The journey into the abyss began with Lotus Symphony. I do like Excel and use it on occasion. But I pine for the days of lean software that did one thing exceptionally well. |
|
They sat on their laurels with 123 v2 for much too long, and competitors surpassed them. v3 wasn't enough more to catch up.
Enable OA's spreadsheet module[1] was certainly head and shoulders above 123, offering real 3D capability (where what Excel views as multiple independent sheets could be addressed directly, so you could do things like have a layer for each month of an annual report, with the topmost being as @SUM() over the column of montly numbers below it), much richer set of functions, and integration with a database and word processor.
And there were others, too. I liked Lucid-3D, which wasn't really 3D but kinda fractal, where you could set up any given cell to drill into a sub-spreadsheet that was used to calculate a single value that would roll up into its parent. And Borland had a competitor, but I don't recall anything about that one.
[1] During college I had a part-time job working on this, on the testing team.
One cool thing we testers did to keep ourselves entertained was to build a spreadsheet casino. Each of us took on a given casino game to implement via spreadsheet macros. My game was blackjack, and it supported the full range of features: multiple decks, double-down, insurance, and all that.
Another guy did craps, the result of which was that we found a subtle bug in the app's random number generator. He set it up to play itself automatically and left it running overnight. When we came back in the next day, he was rich; that's not supposed to happen. He ran the test again the next night, and same thing. The bias in the RNG was causing rolls of 11 to happen more often than they should have.