M Gillett wrote:
> On the hardware side, It seems to me that with the dataset size in your inital
> example, almost any hardware would be ok - apart from a MAC ;-) personal
> hate. I would suggest if future scalability is an issue that you move toward
> a UNIX environment (or LINUX on a PC).
Why the preference for a command line interface. When I switched to Mac after 7
years of DOS, I felt a great sadness at the loss of control ove AUTOEXEC.BAT,
CONFIG.SYS and all those *.INI files.
It lasted about a fortnight.
All of a sudden I discovered what computing was really about ... using
applications. Not tweaking to get things to work just so.
I don't slag off PCs. I still run Windows 95 (on a Mac) and its never crashed
once in thirteen months. We use it to convert M$ Access database files over to
Filemaker on my Mac server.
Whilst Filemaker would probably shudder at the amount of data being bandied
here, there are some seious industrial-strength solutions available - FoxPro and
4D come to mind and there are probably more.
Basically, my message is "don't write the Mac off".
This message was not written on an Apple Macintosh but a UMAX Pulsar running
MacOS.
George Pitcher
SCOPE Project Technical Unit
Napier University, Edinburgh
Tel: (44) 131-455 6179
www.scope.napier.ac.uk/
[log in to unmask]
They said "get a computer with Windows 3.1 or better" so I got a Mac!
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
|