I think there is a general perception that browserify/watchify is slow, cumbersome to setup, frequently serves stale/empty bundles, hides errors in terminal, produces ugly terminal logging, and introduces an otherwise poor developer experience compared to webpack/etc.
I don't feel this way at all, in fact I find browserify better than webpack on all of the above points, but only because I've built and worked on a lot of tools to help avoid these issues. I've added a "See Also" section to try and improve discovery with these tools.
I could take this PR a step further and push budo higher up in the readme. Of course I have some bias here, but in my experience most users do not need to interact with watchify CLI directly, and instead could use budo to provide a cleaner and faster development experience.
I think there is a general perception that browserify/watchify is slow, cumbersome to setup, frequently serves stale/empty bundles, hides errors in terminal, produces ugly terminal logging, and introduces an otherwise poor developer experience compared to webpack/etc.
I don't feel this way at all, in fact I find browserify better than webpack on all of the above points, but only because I've built and worked on a lot of tools to help avoid these issues. I've added a "See Also" section to try and improve discovery with these tools.
I could take this PR a step further and push
budohigher up in the readme. Of course I have some bias here, but in my experience most users do not need to interact withwatchifyCLI directly, and instead could usebudoto provide a cleaner and faster development experience.