3 ms·
Sorry, but it's not like arguing you can use "Gimp rather than Photoshop" at all. You just identified a specialist application that's used in a specific use-ca
by slgeorge 12y ago
Sorry, but it's not like arguing you can use "Gimp rather than Photoshop" at all.
You just identified a specialist application that's used in a specific use-case by a limited user-base who fully use the capabilities of the software. When a designer uses those tools their productivity is significantly increased or limited by the software. The focus of the role is using the computer as a tool, so if it performs poorly so do they.
Most 'general office' users, and certainly many administrators don't fully use the capabilities of the software they have because it's not the focus of their jobs. The software isn't the limiting factor in them doing the job. Take the example of someone working in job centre or similar, they'll likely use a Word processor for providing letters, e-mail for external/internal interaction and some custom internal applications (e.g. the jobs database). There are all well within the capabilities of Open Source software.
Framing it that way would certainly be an argument against replacing Photoshop for Gimp; but it doesn't tell you anything useful about replacing general Windows/MS Office with Linux and Open Source.
- alkonaut 12y agoI think the same argument holds for OO vs MS Office as well. They are much closer than Gimp/PS obviously, but for power users they aren't even close to interchangeable. A good middle ground would be migrating the 95 or 99% who are "casual" users to open source, but you'd then have a heterogeneous system, which isn't ideal. VM's could be used to have all-Linux desktops and still provide users of win-only software with what they need. My point is: the big savings are in the 95% but the big cost is for migrating the last 5%.