Grunt and RequireJS are out, it's all about Gulp and Browserify
100percentjs.com
Grunt and RequireJS are out, it's all about Gulp and Browserify
1–10 of 163 posts
Re: Grunt and RequireJS are out, it's all about Gulp and Browserify
#2... and now we have fez: https://github.com/fez/fez
Re: Grunt and RequireJS are out, it's all about Gulp and Browserify
#3Gulp looks very interesting. Browserify vs. RequireJS seems more complex to me, though - it isn't difficult to use RequireJS in the CommonJS pattern. When I tried Browserify it was incredibly slow to build - but that might have been me setting it up wrong in Grunt...
Re: Grunt and RequireJS are out, it's all about Gulp and Browserify
#4... and now we have fez: https://github.com/fez/fez https://news.ycombinator.com/item?id=7090479
Well (taking cues from the article) it has been a couple of weeks.
This is the first I've heard of Gulp though. Looks promising.
Re: Grunt and RequireJS are out, it's all about Gulp and Browserify
#5Seems like it will be an awful lot of work to support older work?
Re: Grunt and RequireJS are out, it's all about Gulp and Browserify
#6I wouldn't say that. RequireJS vs. Browserify is still a very contentious issue that is up to a developer's preferences.
Re: Grunt and RequireJS are out, it's all about Gulp and Browserify
#7There have been numerous posts stating that Gulp is faster than Grunt. However, the "faster" argument needs to be qualified with "under these conditions ____". Even better, here's my configuration. Here's the processing time of x and of y.
With JavaScript builds in particular, it's important to separate when the task running is used. At least in my workflow, I have two distinct times:
1. Development time 2. Build time
"Development time" is when the task runner is used during development, such as running livereload to update the app with saved changes to source files. Speed during development time is very important.
"Build time" is the time used when building a production package. With build time, if one task runner is 5 sec. vs. 10 sec. it makes little difference.
Is one task runner always faster?
What are the differences in performance?
And are these development time or build time differences?
I'm all for new tooling, but let's have measurements in place so that people can make intelligent decisions about when one vs the other is right/wrong for a given project.
As for configuration complexity, it would be great to see a large production configuration of Grunt and Gulp.
Re: Grunt and RequireJS are out, it's all about Gulp and Browserify
#8Wonder why the website hosting the tutorial mentioned in the article is "on vacation"?
Here's a rather ugly google cache'd version: http://robo.ghost.io/getting-started-with-gulp-2/
Re: Grunt and RequireJS are out, it's all about Gulp and Browserify
#9Gulp looks very interesting. Browserify vs. RequireJS seems more complex to me, though - it isn't difficult to use RequireJS in the CommonJS pattern. When I tried Browserify it was incredibly slow to build - but that might have been me setting it up wrong in Grunt...
I think the author oversimplified the choice of Browserify and RequireJS. They have some overlap, but are not 100% replacements.
Both have the concept of modules, and they overlap in this area.
Browserify allows you to use Node style modules in the browser.
RequireJS allows you to asynchronously load parts of your app, while Browserify bundles all JS into a single file.
Re: Grunt and RequireJS are out, it's all about Gulp and Browserify
#10... and now we have fez: https://github.com/fez/fez https://news.ycombinator.com/item?id=7090479
There is an entire range of build tools. some devs still use `make`, bash &/or hand-written node scripts. Once you have them set up, & keep same folder & msc patterns, they can all be satisfactory.
The advantage of Grunt is that it has a huge ecosystem. But Gulp has many of Grunt's heavy-hitters building plug-ins for it. So you can look at Gulp as front-end-build-tools v3.0 (Addy & Paul Irish were pushing Ant before Grunt).