JohnnyLucky,
It is like the WordPerfect versus WORD wars of only 10 years ago. The ageing population of WP users utterly hated the transition to Word. Now, virtually all are competent. Tools are tools, and very few of the "special features" are really useful in day to day processing. Yet that said, some are critical, especially Photoshop's built-in memory manager, that rather smartly deals with aggregate image area well in excess of physical memory.
For instance ... my brother does digitized large-format work. Average "high-quality" images might be 480 dpi, 30" by 40" ... which if you do the math is (480 x 480 x 4 (bytes/32-bit) x 30 x 40) = 1 gigabyte ... without any layers.
Adding the profusion of layers to the image in PS ... can cause it to easily be a 5 to 10 GB file.
Now ... imagine having it open in the middle of "editing", and simultaneously needed a few dozen other images open (to cut, paste layers, do adjusts). 12-15 GB, easily.
CS skims past this potential roadblock without significant productivity impact. Not so for any operating-system based virtual memory consuming application. GRANTED, soon (say in 5 years) the bog-standard machine will have 16+ GB of memory ... and that brother's work is pretty unusual stuff ... but I'm thinking that CS's 25 year old memory managment philosophy is more sound than the competition who have nothing "special".
It is like the WordPerfect versus WORD wars of only 10 years ago. The ageing population of WP users utterly hated the transition to Word. Now, virtually all are competent. Tools are tools, and very few of the "special features" are really useful in day to day processing. Yet that said, some are critical, especially Photoshop's built-in memory manager, that rather smartly deals with aggregate image area well in excess of physical memory.
For instance ... my brother does digitized large-format work. Average "high-quality" images might be 480 dpi, 30" by 40" ... which if you do the math is (480 x 480 x 4 (bytes/32-bit) x 30 x 40) = 1 gigabyte ... without any layers.
Adding the profusion of layers to the image in PS ... can cause it to easily be a 5 to 10 GB file.
Now ... imagine having it open in the middle of "editing", and simultaneously needed a few dozen other images open (to cut, paste layers, do adjusts). 12-15 GB, easily.
CS skims past this potential roadblock without significant productivity impact. Not so for any operating-system based virtual memory consuming application. GRANTED, soon (say in 5 years) the bog-standard machine will have 16+ GB of memory ... and that brother's work is pretty unusual stuff ... but I'm thinking that CS's 25 year old memory managment philosophy is more sound than the competition who have nothing "special".
Facebook
Twitter