When comparing Pint vs Brunch, the Slant community recommends Brunch for most people. In the question“What are the best node.js build systems / task runners?” Brunch is ranked 6th while Pint is ranked 9th. The most important reason people chose Brunch is:
According to speed benchmarks, Brunch is one of the fastest tools around for compiling files. According to the authors of Brunch the reason behind this speed is that it recompiles **only** the changes that were made to an app and performs extensive caching of the app's code.
Ranked in these QuestionsQuestion Ranking
Pro Uncertainties integration
Transparently handles calculations with quantities with uncertainties (like 3.14±0.01) meter via the uncertainties package.
Pro Supports both Python 2 and Python 3
A single codebase that runs unchanged in Python 2.7+ and Python 3.0+.
Pro NumPy compatibility
It supports a lot of numpy mathematical operations without monkey patching or wrapping numpy.
Pro Supports any numerical type
Supports fraction, float, decimal, numpy.ndarray, etc.
Pro Uses jobs to prevent bloated build files
Using Grunt in complex projects can lead to extremely bloated build files. Pint resolves this issue by introducing Jobs, a job is basically a set of Grunt tasks that are related to a particular build step. Using this method the build code remains organized in different job files, for example one for js compilation and one for CSS preprocessing. When the build process is started, Pint starts running these job files which in turn build the project.
Here's a sample
Pintfile.js further demonstrating the concept of jobs in PintJS.
Pro Faster builds with built-in concurrency
Every job in a build process may depend on something before it. A simple example would be copying of the minified files to the dist directory, this task needs to be performed after the compilation is complete. What Pint does is that it lets the user declare the dependencies within each job in a
dependsOn array. Hence whenever PintJS starts the build process it first generates an internal dependency model so that the build could be parallelized by spawning up new Grunt processes wherever possible resulting in the complete build process being concurrent (and really fast!).
Pro Takes advantage of Grunt's huge plugin ecosystem
Pint is built on Grunt, so it can use Grunt's plugins. Grunt has a plugin for pretty much any need with over 4000 plugins currently available.
Pro Simplified build lifecycle
In some projects there are tasks that aren't related to the build at all. These can be simple tasks such as pulling the GIT SHA or reading the package.json file into variables. With Pint these additional tasks can be defined in the build file too. This is made possible by providing users with an initializr and a finalizr; inside the
initialize callback, tasks such as generation of a list of test files or reading the package.json file can be defined, while in the
finalize callback users can define moving of the build files or pushing the source maps to their server.
Pro Compilation is super fast
According to speed benchmarks, Brunch is one of the fastest tools around for compiling files. According to the authors of Brunch the reason behind this speed is that it recompiles only the changes that were made to an app and performs extensive caching of the app's code.
Pro Time to setup is extremely low
After installing Brunch the next step is to load a skeleton from git.io/skeletons. This step is as easy as installing another plugin from the npm registry, just point Brunch to the path of the required skeleton/generator then wait for it to work out its magic. Next, run
brunch build then wait for a second or two and voila! the project is ready.
Pro The configuration file is small and the configuration itself is fast and easy
Brunch's config files can be extremely small compared to other alternatives. The fact that brunch also allows you to chose from a number of generators also lowers the configuration time considerably.
Pro Concatenates scripts and styles and auto-generates matching source maps
Con Potentially unsupported
No activity on repo in 2 years as of Oct 2015
Con Configuration files are bloated and long
Pint's configuration files are the same as Grunt's. Meaning that they are long and hard to read, especially for new users.