This is awesome but we should address the elephant in the room… GUARD!
In my experience as a front-end dev I still find it a bit difficult to get backend developers to use Grunt because they find the javascript syntax a bit confusing. As frontend developers Grunt is a perfect paradise, but the problem I always run in to when introducing this to backend or non javascript developers is, “Why not just use guard?”.
Of course we all should be using some sort of task runner, but how do we convince folks to use Grunt instead of Guard.
In defense of the Grunt haters, Guard is able to:
$ gem install guard-sass
$ gem install guard-coffeescript
$ gem install guard-livereload
$ gem install guard-concat
$ gem install guard-uglify
Andrew Solomon
This is awesome but we should address the elephant in the room… GUARD!
In my experience as a front-end dev I still find it a bit difficult to get backend developers to use Grunt because they find the javascript syntax a bit confusing. As frontend developers Grunt is a perfect paradise, but the problem I always run in to when introducing this to backend or non javascript developers is, “Why not just use guard?”.
Of course we all should be using some sort of task runner, but how do we convince folks to use Grunt instead of Guard.
In defense of the Grunt haters, Guard is able to:
$ gem install guard-sass
$ gem install guard-coffeescript
$ gem install guard-livereload
$ gem install guard-concat
$ gem install guard-uglify