-=> Quoting Nick Alcock to Stephane Bessette <=-
 NA> What's more; another comparison, oooh... Linux w/ X-Windows. 16Mb+ for
 NA> sensible use.
 NA> SGI IRIX: 32Mb+. Er, no, that's V5.1+... 16Mb+ for any other versions.
 NA> Solaris: 32Mb+
 NA> HP-UX: 48Mb+ (if you're lucky)
        OS/2 v3.0:  8 megs, but 16 is better
        WinNT:  I've often heard that 32 megs was the only way to go
        Win95:  I've heard that 8 megs is barely enough, so 16 megs
        Windows 3.1:  4 megs for simple usage, otherwise 8 megs (MS-Office)
        DOS:  depends on the application (8 megs for most games nowadays)
 NA> The bigger the OS, the bigger the memory requirements. I've designed
 NA> one (in some detail) that needs *gigabytes* of RAM just to *start*.
 NA> (4Gb is the basic config; not much more is needed for apps though
 NA> 'cos it's all componented)
        I find 4 Gb to be quite an enormous amount of memory.  I think
I understand what you mean by componented, but nevertheless, 4 GB!!
 SB> For Windows developpers, or anyone that performs some
 SB> serious tasks, being able to multitask applications is amazingly
 SB> simple to learn, and soon becomes an invaluable capacity.
 NA> 
 NA> I think you'll find that should be 'multiprocess'. Multi*task*ing
 NA> isn't actually all that easy to get used to; the human brain doesn't
 NA> work that way. But a cron, and cronned background jobs/compilations in
 NA> the background &c are a necessity.
        If you think of it as starting a long task (printing, a long
file transfer, a fax) and being able to do something else in the
meantime (read/write a text), then multitasking is not that complicated.
        Stephane [TEAM OS/2]
--- Blue Wave/OS2 v2.20
---------------