Brunch: Replace gulp, grunt and increase your dev speed
1–10 of 58 posts
Re: Brunch: Replace gulp, grunt and increase your dev speed
#2[deleted]
Re: Brunch: Replace gulp, grunt and increase your dev speed
#3[deleted]
[deleted]
Re: Brunch: Replace gulp, grunt and increase your dev speed
#4Huh, I always thought Brunch was more of a Yeoman competitor than Grunt or Gulp.
Re: Brunch: Replace gulp, grunt and increase your dev speed
#5I do appreciate when tools/libraries take the time to explain the problem and how they differ from their competition. Especially in cases like this, where it's an underlying architecture difference.
The various Rake servers (Puma, Unicorn, etc.) have also done a great job of this.
Re: Brunch: Replace gulp, grunt and increase your dev speed
#6I've used brunch for a few years now and found it to be quite performant for my personal projects. Once it's set up it just works smoothly. Getting it set up though with the various plugins you need for your own build process can be a bit of a headache sometimes, and I've felt hedged in at certain points by its largely declarative config. I do think the benefits of its building and caching system are worth it for the standard frontend workflow needs and wish it had more mindshare/general community love.
Re: Brunch: Replace gulp, grunt and increase your dev speed
#7I do appreciate when tools/libraries take the time to explain the problem and how they differ from their competition. Especially in cases like this, where it's an underlying architecture difference. The various Rake servers (Puma, Unicorn, etc.) have also done a great job of this.
>The various Rake servers (Puma, Unicorn, etc.)
nitpick: they're Rack servers. Rake is the ruby make.
Re: Brunch: Replace gulp, grunt and increase your dev speed
#8have always been a huge fan of brunch but lately wanted to take advantage of Gulp and Browserify (https://github.com/mikew/browserify-brunch doesn't really cut it) so I wrote parched[1] and parched-tasks-webapp[2]
Re: Brunch: Replace gulp, grunt and increase your dev speed
#9We use grunt at work, and it starts to pain us. Now that our assets pipeline got pretty big, our whole grunt built takes ~30 sec (+10s just for sass and browserify, each).
I do feel like most of the slowness is the actual compile time though, not because of grunt or whatever runs the compilation.
I'll try to implement brunch and see how it can outperform grunt on this. Hopefully it will make it better!
Re: Brunch: Replace gulp, grunt and increase your dev speed
#10It looks like this document is a work in progress. Were you looking for feedback on the document?
I have used build systems like this (and webpack) so I think I am the sort of person you're looking to win over.
The heavy use of bolding makes this read like a pyramid scam and made it hard for me to take it seriously.
In all documentation, my main feedback is: the more words you use, the less you're respecting your reader. Your goal should be to wordsmith your text down to convey the maximal information in the least space.
You spend a lot of words talking about things about your product rather than talking about your product itself. I was also flabbergasted to discover that popular build systems are not incremental but it'd be more useful to just highlight the distinction and move on. I think it's ok to include a bit of that in your blurb, but even in chapter three you're saying stuff like "We’ve been preaching JS modules for six years" (again with the superfluous bold) which is irrelevant to someone looking to understand what your system does.
For another example, you're asking your users to read three paragraphs of "should I use a skeleton" discussion before ever even giving them any insight into whether your system will work for them. I think you could shave that section down to a sentence or two: (1) to get started, I recommend [X]; (2) more experienced users will prefer a skeleton via the [Y] command [link here to the full documentation].
Writing useful documentation is really hard. Good luck.