Introducing
The Slant team built an AI & it’s awesome
Find the best product instantly
Add to Chrome
Add to Edge
Add to Firefox
Add to Opera
Add to Brave
Add to Safari
Try it now
4.7 star rating
0
What is the best alternative to Grunt?
Ad
Ad
Webpack
All
11
Experiences
Pros
9
Cons
2
Top
Pro
Rich and flexible plugin infrastructure
Plugins and loaders are easy to write and allow you to control each step of the build, from loading and compiling CoffeeScript, LESS and JADE files to smart post processing and asset manifest building.
See More
Top
Con
Config file may be hard to understand
Due to a somewhat hard to grasp syntax, configuring Webpack may take some time.
See More
Top
Pro
Tap into npm's huge module ecosystem
Using Webpack opens you up to npm, that has over 80k modules of which a great amount work both client-side and server-side. And the list is growing rapidly.
See More
Top
Con
Can not load files discovered during runtime
See More
Top
Pro
Can create a single bundle or multiple chunks loaded on demand, to reduce initial loading time
Webpack allows you to split your codebase into multiple chunks. Chunks are loaded on demand. This reduces the initial loading time.
See More
Top
Pro
Supports source maps for easier debugging
Source maps allow for easier debugging, because they allow you to find the problems within the origin files instead of the output file.
See More
Top
Pro
ES6 module support
Webpack supports ES6 modules and their import and export methods without having to compile them to CommonJS require
See More
Top
Pro
Share the same modules client-side and server-side
Because Webpack allows you to use the same require() function as node.js, you can easily share modules between the client-side and server-side.
See More
Top
Pro
Bundles CommonJs and AMD modules (even combined)
Webpack supports AMD and CommonJS module styles. It performs clever static analysis on the AST of your code. It even has an evaluation engine to evaluate simple expressions. This allows you to support most existing libraries.
See More
Top
Pro
Mix ES6 AMD and CommonJS
Webpack supports using all three module types, even in the same file.
See More
Top
Pro
Limit plugin integration issues
See More
Hide
See All
Experiences
Get it
here
107
17
Gulp
All
17
Experiences
Pros
11
Cons
5
Specs
Top
Pro
Large plugin ecosystem
Currently gulp offers a selection of 1000+ plugins and it is growing rapidly.
See More
Top
Con
Dead
Gulp is dead, hasn't been updated in 4 years.
See More
Top
Pro
Focuses on code instead of configuration
This depends on your style, but gulp is closer to the code, the actual execution isn't hidden by multiple layers and it's much easier to customize the build system without writing bloated modules. This also brings rather small configuration files.
See More
Top
Con
Rapidly changing API
While it's good that the gulp maintainers want the api to be as good as possible, it comes at the expense of stability. The upcoming gulp 4.0 release has another update to the way dependency management works which will require everyone to update their build scripts. It also makes it hard to look up information on best practices as the best practices keep changing, making a lot of the blog posts and questions about gulp out of date.
See More
Top
Pro
Allows creating task dependencies
Any task can be set to have other tasks as dependencies. The dependencies are specified through piping streams, and tasks run concurrently if they do not block in dependencies.
See More
Top
Con
You need to know some limitations that are not very intuitive
There are some features in Gulp which may not be very intuitive, or that otherwise should have been the default features instead of having to implement them through arguments. For example, to keep the correct folder structure when you are copying a file, you have to add {base: "lib/"} as an argument.
See More
Top
Pro
It is possible to use projects that use streams without plugins
Since Gulp just uses streams at its core, you don't actually need a plugin wrapper to use a project that uses streams. If you use this approach, the you don't even have to worry about plugin maintenance at all, and get the bleeding edge updates as soon as they come out even if the plugin hasn't been updated. It also means if a project happens to not have a plugin, you don't need to write a new one, you can just use it as is.
See More
Top
Con
No incremental building
See More
Top
Pro
Streaming build system makes it easier to apply code transformations
In gulp, it's easy to pipe multiple steps together which you commonly need with build systems. For example, you may need to compile the javascript source files, then package them together, and then minify it. The streaming system makes this much easier. Additionally, it improves performance since all operations are done in memory (compared to I/O operations) and avoids the need of unnecessarily compiling files (compared to Grunt that has to compile all files even if just one has changed).
See More
Top
Con
Not suited for big and complex apps
Writing gulpfile for complex app which consists of many source types is very cumbersome and flawy process. You'll know when you want to move to webpack.
See More
Top
Pro
Chaining API that's simple and elegant
In Gulp, the transforms are performed through chains which makes it easier to understand the order of operations, and easier to modify it.
See More
Top
Pro
Concurrency allows for high-speed perfomance
Because streams in Gulp use pipes to establish dependency order, they are parallel by default without having to rely on plugins or hacks.
See More
Top
Pro
Minimizes disk operations for improved performance
Because Gulp is built using streams, it can store intermediate transformations in memory and defer writing to disk until the very end. This improves performance by not requiring expensive blocking disk operations for task dependencies.
See More
Top
Pro
The configuration file is easily readable
Gulp's configuration file is actually very readable because it's actual JavaScript instead of a large file of JSON objects. The entry barrier is very low for developers who have never used a task runner before and it's API is very simple, with only 4 methods.
See More
Top
Pro
Gulp modules are usable without Gulp
Because Gulp is built on top of the streaming API, you don't actually need gulp to use them. This could be helpful if you want to re-use those modules outside of gulp, possibly for testing, and using the same modules would be more consistent.
See More
Top
Pro
Gulp tasks run from terminal
See More
Specs
Task instruction style:
code
Hide
See All
Experiences
Get it
here
110
12
RocketCake
All
6
Experiences
Pros
5
Specs
Top
Pro
Offline
You can work offline as RocketCake is an installable Windows or Mac application. It's also possible to publish on a local disk first before uploading to a webserver.
See More
Top
Pro
Wysiwyg
No need for coding.
See More
Top
Pro
Mobile support
Support for e.g. iPhone 8, iPhone 7+, iPhone 8+, iPhone X, Samsung Galaxy S8, Galaxy S8+, LG G4, LG G5.
See More
Top
Pro
PHP and ASP support
It's possible to use PHP or ASP to create dynamic websites.
See More
Top
Pro
Templates
15 free templates to choose from.
See More
Specs
Platforms:
Windows, Mac
WYSIWYG:
Yes
Hide
Free / paid
16
1
Mocha
All
9
Experiences
Pros
7
Cons
2
Top
Pro
Supports different assertion libraries
Mocha runs independently from the assertion library, so you can choose which assertion format works best for you. Mocha most often is run in combination with assertion library Chai.
See More
Top
Con
Can be intimidating for beginners
While some testing frameworks are complete out of the box, Mocha requires developers to select and set up assertion libraries and mocking utilities. For someone who is just starting to learn how to build tests this can be scary as they will also have to choose which libraries to use and learn them too.
See More
Top
Pro
Write tests with Behavior Driven Development (BDD)
Allows developers to choose their development process. Not only TDD but also BDD.
See More
Top
Con
No atomic tests
Tests cannot be ran in random order.
See More
Top
Pro
Runs in Node.js and the browser
Mocha has a browser build as well as a node command line program so you can test in client and server side environments.
See More
Top
Pro
Makes Asynchronous testing extremely easy
No need to write tricky statements for Async testing. Mocha gives you a done callback. Place this done parameter in your callback function, that'll let Mocha know that you've written an asynchronous function.
See More
Top
Pro
Integrates really well with NodeJS
The Mocha test framework itself runs on NodeJS, hence it makes everything related to it extremely simple. With Mocha's simple syntax and speed, testing your node.js app just got a whole lot easier.
See More
Top
Pro
Custom full color test reporters
Mocha has multiple test reporters built in and you can create your own as well. The test reporters have full color and makes it easy to see if your tests fail or not.
See More
Top
Pro
Easy to add support for Generators
Aside from the numerous benefits with generators in your application, You can now also integrate generators into your test suite. By using mocha, all you have to do is enable support for generators.
See More
Hide
See All
Experiences
Get it
here
110
6
Yeoman
All
11
Experiences
Pros
10
Cons
1
Top
Pro
Active community
Yeoman has an active community with new generators being created at a rapid pace. Because of the momentum behind the community, you can expect good support and adoption for new tools and frameworks promptly after they come out.
See More
Top
Con
Combining Yeoman and backend frameworks can bring problems
Combining Yeoman and a backend framework such as Django, Rails or Laravel can create problem because the project structure of Yeoman may not be compatible with that of the backend project. It can be tuned to work but for small projects it can be relatively time consuming.
See More
Top
Pro
Huge number of generators for scaffolding your project
Yeoman generators allow you to quickly set up a new project. Invoked with the scaffolding tool 'yo' they provide a boilerplate & tooling selection. There are over 1000 generators, including generators for ember, angular & backbone, to choose from, the majority of which are community maintained.
See More
Top
Pro
Allows you to choose between different build systems
Yeoman supports both major build systems - Grunt and Gulp. These build systems will help you automate tasks such as minification & concatenation of files, running tests, deploying and live-updating your webpage among many others.
See More
Top
Pro
Free and open source
Yeoman is free, open source and licensed under BSD.
See More
Top
Pro
Support for the package manager of your choice
Yeoman supports both Bower and npm, and is flexible in regard to tools to allow it to work with a wider range of project requirements.
See More
Top
Pro
Standardized workflow process
Yeoman wants webapp development to be more standardized under the "Yeoman workflow" banner. As such it encourages the use of a specific combination of tools - a scaffolding tool (yo), a build tool (grunt, gulp, etc) and a package manager (bower, npm).
See More
Top
Pro
Generators can be composed with other generators
Yeoman's scaffolding system allows generators to rely on other generators allowing for better code reuse and standardization between generators that use a common sub-component.
See More
Top
Pro
Cross-platform
As a command line tool it works on OS X, Linux & Windows.
See More
Top
Pro
Works with the package manager directly
Yeoman doesn't just scaffold your project, but also helps you integrate with your package manager directly, so you can manage your entire project with it.
See More
Top
Pro
Developers can create their own plugins
Developers can also create their own Yeoman generator which are practically plugins with which Yeoman works. Generators are basically Node.js modules and can be created just like any other Node module. There is also a very detailed and useful guide on how to create a generator on the Yeoman official website.
See More
Hide
See All
Experiences
Get it
here
43
3
Fly
All
8
Experiences
Pros
6
Cons
1
Specs
Top
Pro
Takes advantage of ES6 features
Fly is written to use new ES6 features like generators and promises.
See More
Top
Con
Limited number of plugins
There's still a very limited number of Fly plugins. This can contribute negatively in development time and energies spent to make a plugin to complete a task for which there's none yet.
See More
Top
Pro
Support for concurrent tasks
Fly supports parallel processing and concurrent tasks via Fly.prototype.start([tasks], { parallel: true })
See More
Top
Pro
Smaller build files, with same benefits of a huge one
If it's a fly- plugin you don't have to require it like you do with every other build tool. Theres no need for wrapper functions for each plugin (aka .pipe()). If it's a fly- plugin you just call it directly. The build file get's to the point quickly without adding all the extra fluff. This makes your build file very clean and easy to read!
See More
Top
Pro
Very easy to setup
Fly is easy to setup, there are no caveats that you have to know since everything is very intuitive. Also with fly you don't have to repeat your self several times. You just define out what you want and that's it. If it's a fly plugin it will be required automatically without the need for an additional plugin.
See More
Top
Pro
Fly plugins are required automatically
If you want to use a Fly plugin in a flyfile, it's automatically required without needing an additional plugin.
See More
Top
Pro
Can run subtasks inside a task
Fly supports running multiple subtasks in a single task without having to create a new one.
See More
Specs
Number of Plugins:
~5
Task instruction style:
Code
Processing method:
Pipeline
Hide
See All
Experiences
Get it
here
3
0
NPM
All
15
Experiences
Pros
7
Cons
7
Specs
Top
Pro
Compatible with any CLI
NPM is compatible with any CLI the developer wants to use.
See More
Top
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)
See More
Top
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.
See More
Top
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.
See More
Top
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.
See More
Top
Con
Passing parameters is awkward
In order to pass additional parameters to npm you must add them after -- (e.g., npm run build -- --custom='foo').
See More
Top
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.
See More
Top
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.
See More
Top
Pro
Part of node.js distribution
See More
Top
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.
See More
Top
Pro
You're most likely using NPM already
See More
Top
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.
See More
Top
Pro
Uncomplicated package management system
When it works...
See More
Top
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.
See More
Specs
Number of Plugins:
100.000+
Task instruction style:
Configuration
Processing method:
Pipeline
Hide
See All
Experiences
Get it
here
58
7
Brunch
All
5
Experiences
Pros
4
Specs
Top
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.
See More
Top
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.
See More
Top
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.
See More
Top
Pro
Concatenates scripts and styles and auto-generates matching source maps
Brunch automatically produces a source map for all javascript files and CSS stylesheets whenever it minifies an app's resources. This little feature is extremely helpful when debugging is required at the client end.
See More
Specs
Number of Plugins:
~100
Task instruction style:
Code
Processing method:
Pipeline
Hide
Get it
here
18
3
Chrome Dev Editor
All
4
Experiences
Pros
3
Cons
1
Top
Pro
Git
Built in Git support.
See More
Top
Con
Bugs
The latest versions seem to be buggy.
See More
Top
Pro
Offline
Can run offline.
See More
Top
Pro
Has lots of good templates for getting started
See More
Hide
Free
6
1
Yarn
All
12
Experiences
Pros
11
Cons
1
Top
Pro
The same results will be yielded every time yarn is run in a repository
One of the most important aspects of Yarn is determinism (predictability). The lock file ensures that the same dependencies will always be installed in the same way and order regardless of the machine for a given repository.
See More
Top
Con
Takes up disk space
Yarn adds to your disk space usage since it stores dependencies locally.
See More
Top
Pro
Can tell you why a package was installed
yarn why <query> can tell you why a package was installed and what other packages depend on it.
See More
Top
Pro
Good network performance
Yarn efficiently queues up requests and avoids request waterfalls in order to maximize network utilization.
See More
Top
Pro
Offline mode
If you've installed a package before, you can install it again without any internet connection.
See More
Top
Pro
Flat Mode
Resolve mismatching versions of dependencies to a single version to avoid creating duplicates.
See More
Top
Pro
Multiple registries
Install any package from either npm or Bower and keep your package workflow the same.
See More
Top
Pro
Network resilience
A single request failing won't cause an install to fail. Requests are retried upon failure.
See More
Top
Pro
Good documentation
It looks like it has good documentation.
See More
Top
Pro
Security is put at the forefront
Even though it's still in its early stages of development, security is one of the core values on which Yarn is built. It uses checksums to verify the integrity of every package before executing its code. This also helps avoiding errors related to faulty caching or captive portals. Further steps are also being taken to improve the security of Yarn which will be implemented in the future.
See More
Top
Pro
Built by the community for the community
Even though it's backed by Facebook, Yarn is built as a community project first and foremost. It's completely open source and hosted on Github. It's released under a standard open source client and has its own GitHub organization and set up to work under the same governance model that other successful projects have used in the past, such as Rust and Ember. All of this means that both existing and new contributors will always work together to improve the product and introduce new features while also keeping in mind suggestions coming from the community.
See More
Top
Pro
Backed by Facebook and Google
Was created in a collaboration of Facebook with Exponent, Google and Tilde.
See More
Hide
See All
Experiences
FREE
53
8
Broccoli
All
7
Experiences
Pros
3
Cons
3
Specs
Top
Pro
Brocfile fairly straightforward and small
See More
Top
Con
Windows not fully supported
See More
Top
Pro
Rebuilds are really fast
In larger apps rebuilds get slower and slower as the size of the application increases. Broccoli deals with this by building only the files that were changed and intelligently figuring out their dependencies. This leads to rebuilds being of O(1) constant-time (in Software Engineering terms).
See More
Top
Con
Assumptions about your project limit what you can do
Assumes you want to always output to single output directory. This directory must not exist at the time of running. It also (therefore) can't be your current directory. This puts broccoli slightly out of the class of a truly general "task runner".
See More
Top
Pro
Chainable plugins
With broccoli developers can chain plugins. var tree = broccoli.makeTree('lib') tree = compileCoffeeScript(tree) tree = uglifyJS(tree) return tree
See More
Top
Con
Small community
Broccoli's community is still relatively small and not very active, at least compared to it's competitors. This leads to fewer plugins, guides and less support from developers for any problem that you may face using Broccoli.
See More
Specs
Number of Plugins:
200+
Task instruction style:
Configuration
Processing method:
Pipeline
Hide
See All
Experiences
Get it
here
5
1
GNU Make
All
5
Experiences
Pros
3
Cons
1
Specs
Top
Pro
Uses the full power of the UNIX shell
Make takes advantage of the powerful UNIX shell, using it at it's full potential. STDIN and STDOUT are especially useful because of their versatility.
See More
Top
Con
Doesn't run on Windows by default
Make requires Cygwin/msys2/MinGW to run on Windows.
See More
Top
Pro
No need for wrapper modules
Other build tools need wrapper modules to do certain tasks. The biggest disadvantage of these wrapper modules is that they bind you to a version of that tool. With Make you don't have that problem, there's no need for wrappers and no tools to bind you to a version, you can use any version of Make that you want.
See More
Top
Pro
Works with more than just node.js
Since it's written in C and can be found in all UNIX-based systems it can be used on platforms other than node.js.
See More
Specs
Platforms:
Unix, Linux, Windows, Mac
Hide
Get it
here
56
13
Pint
All
11
Experiences
Pros
8
Cons
2
Specs
Top
Con
Potentially unsupported
No activity on repo in 2 years as of Oct 2015
See More
Top
Pro
Uncertainties integration
Transparently handles calculations with quantities with uncertainties (like 3.14±0.01) meter via the uncertainties package.
See More
Top
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.
See More
Top
Pro
Supports both Python 2 and Python 3
A single codebase that runs unchanged in Python 2.7+ and Python 3.0+.
See More
Top
Pro
NumPy compatibility
It supports a lot of numpy mathematical operations without monkey patching or wrapping numpy.
See More
Top
Pro
Supports any numerical type
Supports fraction, float, decimal, numpy.ndarray, etc.
See More
Top
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.
See More
Top
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!).
See More
Top
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.
See More
Top
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.
See More
Specs
Number of Plugins:
4000+
Task instruction style:
Configuration
Processing method:
File-based
Hide
See All
Experiences
Get it
here
8
3
Google Web Designer
All
4
Experiences
Pros
1
Cons
2
Specs
Top
Con
It is not a tool for website design
It's only for animations, banners and so on.
See More
Top
Pro
Multi platform
Google Web Designer supports Mac, Windows and Linux.
See More
Top
Con
Currently in Beta
Google Web Designer was launched in 2013, and still remains in beta.
See More
Specs
Platforms:
Windows, Mac, Linux
WYSIWYG:
Yes
Hide
Get it
here
4
2
JSHint
All
5
Experiences
Pros
3
Cons
2
Top
Con
No way to support ESnext
There's no support for ESnext available.
See More
Top
Pro
Customizable ruleset
Since it's creation, JSHint was created to be a more configurable version of JSLint (it's actually a fork of JSLint itself). Every rule is configurable through a configuration file.
See More
Top
Con
Difficult to know which rule is causing an error
Because it does not display the rule name that is being broken, it's difficult to know which rule is actually causing the error.
See More
Top
Pro
Comes with support for many librariers
JSHint supports libraries like QUnit, NodeJS, jQuery, Mocha out of the box.
See More
Top
Pro
Basic ES6 support
Basic ES6 support is included.
See More
Hide
Get it
here
12
6
Google Chrome
All
42
Experiences
Pros
22
Cons
19
Specs
Top
Pro
Excellent HTML 5 feature support
See More
Top
Con
Online tracking by default
Chrome allows opting out of tracking by going to Settings > Advanced > Privacy and un-checking any unwanted services. Alternatively Chromium can be used to get a similar browser experience without Google's services on top of it.
See More
Top
Pro
Syncs between devices
By logging into Chrome using a Google account it's possible to sync history, extensions, passwords, bookmarks and other settings between devices. This makes it great for anyone working with multiple devices as it allows experiencing consistent context when in the browser.
See More
Top
Con
Huge memory hog
Each tab and extension in the browser uses significant chunks of RAM, giving the browser poor performance on machines without enough RAM to supply.
See More
Top
Pro
Simple user interface
For example, the address bar is also the search bar. Google calls it Omnibox.
See More
Top
Con
Bad for battery life
Drains battery life on both Windows laptops and Macs much quicker than the alternatives. It can shave hours off the battery life of any non Chromebook laptop.
See More
Top
Pro
Great built-in developer tools
Chrome comes with built-in developer tools, making testing and enhancing web pages simpler for those of us involved in working with such technologies. As well as being beneficial to developers, this also has some benefit to non-technical users; in that by making testing simpler for developers those developers are more likely to use Chrome for their tests, and can spend more time making improvements over investigating underlying causes of issues.
See More
Top
Con
Not fully open-source
While most of Chrome is open source: Chrome does have some closed-source components to make it possible to play some closed media formats.
See More
Top
Pro
Plenty of extensions
There are far more available on this browser than any other, and that may matter for some.
See More
Top
Con
Increasingly slow
When Chrome first came out, it was known for being lightweight and very speedy. Over the years, more and more features have been added to Chrome. Because of this, crashes, errors, and general laggy-ness has increased noticeably.
See More
Top
Pro
Good performance
According to TopTen Reviews, Chrome is currently one of the best performing browsers for initial (cold) startup, average startup, and navigation times. Works very well with the uBlock Origin adblocker.
See More
Top
Con
It's Google
Data collection!
See More
Top
Pro
Automatically updates
Chrome updates in the background ensuring you're always on the latest version. This makes it much more likely that sites will work on your browser, since (almost) all Chrome users will be running exactly the same version.
See More
Top
Con
No mobile extensions
Chrome on Android and iOS does not support extensions.
See More
Top
Pro
Multiple account login
You can have multiple Chromes with different accounts logged at the same time. And it is really easy to manage different accounts.
See More
Top
Con
Not as customizable as Firefox or Vivaldi
See More
Top
Pro
Works great with many extensions
Unlike Firefox, Google Chrome can keep its fast performance regardless of how many extensions are installed. With more than 10 extensions Firefox gets slower and slower in a geometric progression rate. Google Chrome doesn't care how many extensions the user has installed - 3 or 133 it still performs great.
See More
Top
Con
Big target for hackers
Chrome is the most popular browser in the world. That makes it the most targeted browser in the world by hackers.
See More
Top
Pro
Customizable by user
Each of the managed users can have their own configuration (themes, extensions, ...)
See More
Top
Con
Hard/impossible to transfer passwords to a different machine without uploading them to Google
See More
Top
Pro
Can translate text directly
See More
Top
Con
Bad quality control on extensions
Some just plain don't work while a few actually break the browser.
See More
Top
Pro
Uses Blink
It uses the blink rendering engine which has removed many legacy khtml/webkit code to be much lighter and faster.
See More
Top
Con
Basic
Unlike Brave and Vivaldi which are more stable and have more features, Chrome is pretty basic.
See More
Top
Pro
Only one distributor
Unlike those various unofficial Chromium builds, there is only one distributor, so all Chrome releases follow the same standards.
See More
Top
Con
Blurred fonts on Windows
Fonts on Windows are blurred, that is especially noticeable in light fonts on dark background. Small italic text is hard to read.
See More
Top
Pro
Sandboxed Tabs
Every tab runs as their own process, so if one crashes or becomes unresponsive, the whole browser isn't affected.
See More
Top
Con
No menu bar on Windows
There's no menu bar, except on Mac OS or Linux appmenu.
See More
Top
Pro
Chrome is faster than Firefox
See More
Top
Con
Does not hardware accelerate HTML5 video correctly
Chrome is unable to hardware accelerate HTML5 video correctly which makes playing 4k video on laptops a poor experience filled with lag. Though there is a workaround for YouTube in that a plugin can be installed to force Flash playback instead of HTML5, which plays smoothly and has no HW acceleration issues. There's another plugin (h264ify) that will force to use the h.264 codec video if available instead of the VP9 one which is the resource hog.
See More
Top
Pro
Simple interface
See More
Top
Con
No reader view
Unlike most other browsers, Chrome doesn't have a reader view function.
See More
Top
Pro
Data collection
Chrome uses online services to collect our data and improve our browser experience. But this also means it spies on you.
See More
Top
Con
American agents may track you
See More
Top
Pro
Engine is open-source
Chromium is open source, except the proprietary media codecs like AAC, H.264, MP3 and Adobe Flash, that can't be legally open-sourced.
See More
Top
Con
Soon to disable AD blocking and create DRM for the web
See More
Top
Pro
Popular
As of March 2015, Chrome is the most popular browser on the internet, with a 43.9% - 63.7% market share, Its rendering engine Blink is also the most used rendering engine and used in many products including: Opera, Vivaldi, Qt, Brave, Steam or Electron meaning most developers will be testing their sites against this browser to ensure compatibility.
See More
Top
Con
Gives too much weight to Google on the future of the Web
See More
Top
Pro
Backed and supported by Google
Whilst Chrome is based on the open source browser Chromium, Google reviews this code and build on top of it. This means it takes (and contributes to) a number of the benefits of the open source model whilst having the resources, support and investment of a major company.
See More
Top
Pro
Plays more media formats than any open source browser
Includes support for many licensed unfree media formats.
See More
Top
Pro
Multimedia Plugins and Codecs included
Google Chrome comes with its own flashplayer and the most common multimedia codecs so you don't have to worry that they are outdated nor do you need to install them as a third party package.
See More
Specs
Platforms:
Linux, MacOS, Windows, Android, iOS
License:
EULA
Based On:
Chromium with proprietary Media codecs and Addons
Browser Engine:
Blink, Webkit on iOS (since Apple does not allow third-party web engines)
See All Specs
Hide
See All
Experiences
free
780
490
Gobble
All
4
Experiences
Pros
2
Cons
1
Specs
Top
Pro
Debuggable
Using Gobble is even easier when you consider the fact that it's extremely debuggable.
See More
Top
Con
Still in active development
Since Gobble is still in active development it's API may change and it's documentation is not fully ready yet.
See More
Top
Pro
Very easy to write plugins
Gobble's API is very easy to learn and very intuitive. This makes it very easy for developers to write different plugins for tasks that they may need.
See More
Specs
Number of Plugins:
~50
Task instruction style:
Configuration
Processing method:
File-based
Hide
Get it
here
0
1
Built By the Slant team
Find the best product instantly.
4.7 star rating
Add to Chrome
Add to Edge
Add to Firefox
Add to Opera
Add to Brave
Add to Safari
Try it now - it's free
{}
undefined
url next
price drop