sublimious vs Gulp
When comparing sublimious vs Gulp, the Slant community recommends Gulp for most people. In the question“What are the best plugins for Sublime Text?” Gulp is ranked 24th while sublimious is ranked 30th. The most important reason people chose Gulp is:
Currently gulp offers a selection of 1000+ [plugins](http://gulpjs.com/plugins/) and it is growing rapidly.
Specs
Ranked in these QuestionsQuestion Ranking
Pros
Pro Pre-configured with layers
Whenever you need to work on a new language that you don't have plugins for yet, you can choose to check if sublimious has a layer for that language. If it does, all you need to do is activate it and sublimious will automatically download all plugins you need for that language, add keybindings for efficient usage and set the optimal settings for these plugins.
Pro VIM centric
This plugin is perfect for VIM fanatics. It tries to add VIM keybindings to everything, even to where you didn't know it was possible like the sublime text overlay or the sidebar
Pro Ergonomic shortcuts
sublimious adds shortcuts that actually make sense. "p f" for example searches files in the current project. "g s" executes "git status" and so on, you get the idea. It even comes with a helper that shows you what shortcuts are available.
Pro Large plugin ecosystem
Currently gulp offers a selection of 1000+ plugins and it is growing rapidly.
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.
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.
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.
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).
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.
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.
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.
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.
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.
Pro Gulp tasks run from terminal
Cons
Con Dead
Gulp is dead, hasn't been updated in 4 years.
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.
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.
Con No incremental building
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.