-
1. Re: Suggestion - module installation - make PS less bloated, more Pro
-Agfaclack- Mar 22, 2012 5:14 PM (in response to takennick)question is... do you see a real benefit when we have 2 TB harddisks?
ok on my SSD every GB counts... it´s only 240 GB.
but on the other side you have to code/test more when you can disable things like video or 3D.
or you may run into problems when features depend on eachother.
beside that.. that would mean a complete rewrite i guess.
i doubt adobe will waste resources on that.
-
2. Re: Suggestion - module installation - make PS less bloated, more Pro
takennick Mar 22, 2012 5:18 PM (in response to -Agfaclack-)It's about design esthetics and efficency, start up times, and RAM. My issue is it is no longer "photoshop", but "general graphics utility". The hardware is much more powerful these days, but the software gets more bloted and bloated to offset the "excessive" CPU cycles, I guess.. Photoshop 4 was about 65MB. I don't need 80% of the current features for webdesigners and "digital painters" if I work with photos only. Not to mention the type enginge, layer styles and all related tools that have nothing to do with photography.
-
3. Re: Suggestion - module installation - make PS less bloated, more Pro
-Agfaclack- Mar 22, 2012 5:27 PM (in response to takennick)i understand you.. but because some don´t need it they will not rewrite everything.
i am in the same position with 3D max.. we wait for years that they rewrite and clean up the code.
but that would eat up so much resources that they will not do itinstead they replace parts of the code.
There should be modules for Designers, Photographers, Digital Artitsts, Video editors
if you see something like that.... im sure it will be a new product.
-
4. Re: Suggestion - module installation - make PS less bloated, more Pro
PECourtejoie Mar 25, 2012 5:04 AM (in response to takennick)Hello!
I can understand the need for hard disk space with SSDs, but most of the time, having more video abilities will not slow down the photographic ones. The type engine now gets initialized only when you use it, as previously it was done at boot time (this is a CS3 or CS4 change, I don't remember)
The issue with feature segmentation is that some photographers needs text, use layer styles for their watermarks. Some output to the web, and do the webgalleries, while other design the interface as well. Some paint on their Photos, others not... Where and how do you decide what is Photographic, design, etc?
And Adobe has designed an app for Photographers only: Lightroom (and it got text, webgalleries, etc.)



