I just installed IBM® Lotus® Symphony™. I don’t have the pokiest PC on the block, but in order to make it run at any speed at all, you’d need to have a bit of grunt in your PC. My VIA SP13000 box takes a couple of minutes just to bring up the main window.
To be fair, OpenOffice isn’t the fastest starter either; none of them have large bits of themselves running in the Windows system code, unlike MS OfficeThey both work, and are free – and Symphony looks a deal prettier than OpenOffice. As there’s no Mac version of Symphony yet, I’m unlikely to switch just yet.
You’ve maybe heard about this ‘open source’ thing? You get one guess who wrote most of the theory and propaganda for it and talked IBM and Wall Street and the Fortune 500 into buying in.
— the enormous ego of Eric Raymond, responding to a job offer at Microsoft.
Apologies to our neighbours for my testing the Wheelwriter this morning. This is what I found out about it (after having to compile in parallel printer support to the kernel, grr):
Do we need CRs? : yes
Does it talk ASCII? : yes, subset
Bidirectional? : yes
I chickened out and installed the Courier 10 printwheel just so I could use spaces to line things up. I don’t like Courier at all, but at least it’s easy to manage.
It’s strange that, in this age that we are creating information at an unparalleled rate, we’re also losing it just as fast. While IBM Wheelwriter codes from the late 1980s do not represent the lost wisdom of the ancients, it is something of our knowledge, and once lost, diminishes us all.
Therefore, send not for whom the (carriage return) bell tolls; it tolls for thee …
— The above written on an IBM Wheelwriter 10 Series II, using the Thesis PS printwheel.
DB2 just gave me this far from helpful error
DB21034E The command was processed as an SQL statement because it was not a
valid Command Line Processor command. During SQL processing it returned:
SQL0010N The string constant beginning with "'" does not have an ending
string delimiter. SQLSTATE=42603
As a human, or a close facsimile of one, I don’t need to
know the internal server codes
SQL0010N. I don’t need to know that the command was
processed as an SQL statement, because that’s what I was
hoping it would be all along. And I definitely don’t want
to know that SQLSTATE is 42603, for I’m not sure if it
would be very much better or worse if it were 42604. Or 2.
Or, for that matter, 999999999996.
And all this for mismatched quotes around a string.