When comparing Photoshop vs NPM, the Slant community recommends NPM for most people. In the question“What are the best web design tools?” NPM is ranked 15th while Photoshop is ranked 19th. The most important reason people chose NPM is:
NPM is compatible with any CLI the developer wants to use.
Ranked in these QuestionsQuestion Ranking
Pro Industry standard
Photoshop is used by professionals everywhere in a wide variety of fields including photography, graphic design and digital art. It is the de facto standard for image manipulation. If you've seen a magazine ad featuring a model, you've probably seen the effects of Photoshop. You won't be alone when using Photoshop.
Pro Trove of plugins that extend functionality are available
A wide variety of plugins that add new effects, improve existing functionality and simplify workflow are available.
Pro Lots of tutorials
There's a huge number of both free and paid tutorials available online. Websites like Lynda.com offer premium high-quality, in-depth tutorials, but there are plenty of free alternatives to be found on YouTube, blogs and specialized sites on the Internet.
Pro Includes powerful content-aware tools
Photoshop includes content-aware tools such as content-aware fill that can fill in a select area based on what surrounds it.
Pro Packs a staggering amount of functionality
Photoshop is the most fully featured image editing software available today allowing you to perform highly advanced image manipulation.
It has tools for RAW image adjustments, lens correction, retouching, image stitching, HDR, fixing framing. It supports most professional color modes and file formats. It includes extensive lists of filters, styles, effects, fonts as well as tools for painting, sketching and typography work. It understands both raster and vector graphics. It even includes tools for video editing, working with 3D objects and support for 3D printing.
Pro A cheaper, standalone version called Photoshop Elements is available
A stripped down version of Photoshop, called Photoshop Elements can be bought as a standalone application for $100.
Pro Integrates with Creative Cloud
You can save all projects directly to the Creative Cloud allowing you to access them from any device and with any relevant Adobe software.
Pro Creative Cloud Photography subscription includes Lightroom
Lightroom is another image editing software from Adobe that's specifically designed for photo editing and managing of large quantities of digital images.
Pro Compatible with any CLI
NPM is compatible with any CLI the developer wants to use.
Pro Plenty of helpful NPM modules/plugins
NPM has a strong community that has developed plenty of libraries and plugins that are useful to developers.
Pro Very concise configuration
NPM scripts require fewer lines of code to run a given task. This is true even when it's for running build processes. Using Unix pipes lots of tasks can be reduced to one-liners.
Pro Does not need any wrapper modules
With other task runners, you need to install wrapper modules for tools you may already have installed. When using NPM that's not necessary, to use the tools you need, just install them directly through NPM.
Pro Part of node.js distribution
Pro You're most likely using NPM already
Pro Uncomplicated package management system
When it works...
The standalone version of Photoshop costs $19.99/month, though it can be leased as part of the Creative Cloud Photography bundle that includes Lightroom for $9.99/month.
Con Latest versions of Photoshop are subscription-only
While you can still buy CS6 from 2012 without needing a subscription by contacting Adobe support or the cut-down Photoshop Elements, any full-version version of Photoshop past CS6 requires a subscription.
Con Learning it can take some time
While you can relatively quickly learn how to perform a few basic image editing tasks, understanding Photoshop's ins and outs can be difficult. It's partially due to the sheer amount of functionality that Photoshop packs (and understanding that some of the advanced functionality can take a while to understand on its own), and partially due to it being aimed at professionals with little hand-holding for novice users.
Con Batch editing of images is not straightforward
Photoshop is designed to work extensively on one image at a time and while batch editing support exists, it's not that intuitive to use.
Con Affinity Photo is just as good at a fraciton of the price
Switching from Photoshop to Affinity Photo and it's hard to notice the difference quality of a professional's work. They say that PS is the industry standard, but so very few pros that tried Affinity Photo ever look back.
Con Asset management capabilities are lacking
In Photoshop asset management is done through a separate program called Bridge. As Bridge is supposed to be a file management tool for not just Photoshop's files, but for files generated by all of Adobe's applications it covers a breadth of capabilities, but not depth.
Con Custom tasks require additional keyword 'run'
Only a few standard tasks support being executed without the
run keyword (e.g.,
npm start vs
npm run customtask)
Con Not a build system, only a task runner
It is supposed to be used for running gulp, webpack or whatever. But it is not supposed to be used as a build system.
Con Passing parameters is awkward
In order to pass additional parameters to npm you must add them after
npm run build -- --custom='foo').
Con Badly documented
Less than bare minimum official documentation leaves users in the dark without taking often expensive external courses. Even the --help text has unpluggable gaps. One official source notes the documentation isn't adequate yet nothing has been done to fix this.
Con Lot of issues with authentication and random node problems
Unable to recover from common depencies conflicts consistantly. Error messages are not always helpful to debugging. Doesn't account well for users with different versions of node.
Con Does not run well with Windows
Since a lot of projects that use NPM as a build tool most of the time make use of Bash scripts as well. This means that open source projects that run the command
npm run may run into issues when used in a Windows environment.
Con Doesn't allow you to create build process with complicated logic on its own
In complex heterogeneous app you will quickly migrate to gulp, webpack or whatever leaving to NPM only simple task running responsibility.