Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Brunch: Replace gulp, grunt and increase your dev speed

github.com

Post reply on HN
Print view View original

11–20 of 58 posts

Re: Brunch: Replace gulp, grunt and increase your dev speed

#11

Post by paulmillr »

evmar wrote: post #10

It 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 rea…

Thanks for feedback! We'll adjust some wording. We are always looking for ways to improve the docs / product.

Re: Brunch: Replace gulp, grunt and increase your dev speed

#12

Post by Keats »

jypepin wrote: post #9

We 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!

Are you using libsass? The latest release is pretty much at the same level in terms of features than the ruby one and should be much faster

Re: Brunch: Replace gulp, grunt and increase your dev speed

#13

Post by ben336 »

jypepin wrote: post #9

We 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!

If you're doing the whole thing every time, that would be your biggest problem, regardless of tools. It sounds like Brunch does incremental builds out of the box, which would definitely help you, but you can setup Grunt or gulp to do the same thing. It just takes a little work.

We do that with gulp, and after the initial file runs (~8-10 seconds), updates are instant every time.

Re: Brunch: Replace gulp, grunt and increase your dev speed

#15

Post by plorkyeran »

evmar wrote: post #10

It 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 rea…

I agree strongly with everything here. I'm a fan of Brunch and would use it again if I ever work on another project where it'd be relevant, but if it wasn't for that I would have instantly written off Brunch after reading this introduction.

Re: Brunch: Replace gulp, grunt and increase your dev speed

#17

Post by pjungwir »

bryanlarsen wrote: post #16

You definitely need a comparison with webpack. As far as I can tell from a quick scan, webpack has all of the capabilities that brunch does. More importantly, it's much more popular, so the plugins and help you need are likely to be available.

When I read about JS build tools online all I see is grunt/gulp, but when I talk to JS folks in person I keep hearing about webpack and how it does everything they need. Lately my frontend work has used ember-cli for all this stuff, but the next chance I get I'll give webpack some attention.

Re: Brunch: Replace gulp, grunt and increase your dev speed

#18

Post by jorblume »

The worst part about web dev is the amount of time spent investigating every little new tool that comes out. It could be useful, it could not, how do you know unless you investigate it yourself? You could easily spend 20+ hours a week just evaluating tools. And not only that, but some of the most adopted tool aren't performant. Grunt sucks. It really does. Angular is needlessly confusing and overly complex for what it actually does. It also doesn't scale and you need to get super hacky with it to perform properly. You spend more time trying to learn new tools than you do actually coding, then find out the tools aren't even well thought out.

Then what happens when you leave your position and someone comes in a year later? Oooh, that sass preprocessor doesn't work? What's an angular, some kind of measuring tool? The entire system has a "doesn't matter I'll be at the next startup in 2 years" kind of feel to it.

I should really move into Java or C....

Re: Brunch: Replace gulp, grunt and increase your dev speed

#19

Post by Raphmedia »

jypepin wrote: post #9

We 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!

We switched to gulp and changed the workflow so that it's very fast now. Brunch sounds nice, but we just changed from grunt to gulp, so I doubt anyone has the energy to make the switch once again.

Re: Brunch: Replace gulp, grunt and increase your dev speed

#20

Post by 1235971235 »

Created an account for this post only.

As a novice javascript programmer, I am hugely confused by the variety of tools being recommended on Hacker News. Choosing and setting up tooling was harder than writing my first app in React. Not a new complaint, I know, but:

Is there anything like a best practice in modern javascript development that someone can point me to? Or is there a site that gathers the setups used by prominent front-end developers? Thanks for any advice.

Post reply on HN