How often do you have so many dependencies in a web app that you actually need something like RequireJS or Browserify?
Grunt and RequireJS are out, it's all about Gulp and Browserify
61–70 of 163 posts
Re: Grunt and RequireJS are out, it's all about Gulp and Browserify
#62There 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 tim…
gulp is always going to be faster than grunt as long as grunt writes temporary files to disk. Using 3 plugins processing 20 files as an example: grunt will do 60 reads, 60 writes while gulp will do 20 reads, 20 writes
Re: Grunt and RequireJS are out, it's all about Gulp and Browserify
#63... and now we have fez: https://github.com/fez/fez https://news.ycombinator.com/item?id=7090479
To be honest, I wish people would stop mentioning this project until it actually usable for real projects. I have attempted to build a sass task for Fez and failed when I realized that the core project simply does not have the ability to be configured to do very simple things. In the case of the sass plugin, Fez does not support globs, making it difficult/hacky to properly ignore files prefixed with "_", a well-known…
Indeed, fez is not quite completely ready yet - its still in the development / experimental stage.
Re: Grunt and RequireJS are out, it's all about Gulp and Browserify
#64This is a tangential question, but how do front-end people feel about the constant change in the field? I worked in the front-end and followed the trends for years and have found the changes difficult to follow. In 1997, the rage was VB and lots of cottage companies set up and advertising custom ActiveX widgets, on the web one had to learn ColdFusion and HTML/CSS. In early 2000's, VB6 was retired in favor of .net and…
Full-stack dev that came up through the front-end ranks here - I'm in my early 30s and have been doing this in some form or another for 17 years. I started with Perl and C CGI scripts, worked with Java Swing (on the desktop) for a while, had a brief foray into MFC, did a whole bunch of PHP in college, switched to Django/JQuery while working on my startup, and now use a whole bunch of Google-proprietary techniques alo…
I agree with all but will point out that a benefit to a framework or any extensible tool is community contributions and opting out to native means that you don't get that benefit. That being said, when javascript ES6 modules land it'll be much easier to reuse code and dependency on big libraries would be unnecessary, meanwhile you can use Browserify or Component that have a lot of community contributions with minimum dependencies on big frameworks or libraries
Re: Grunt and RequireJS are out, it's all about Gulp and Browserify
#65And just like that I have one more reason to ignore them both and use Make. Speed? Check. Simpler syntax? Check. No need to "fix" code that isn't broken? Check. No need to waste my attention on every new fad? Check.
Why even use Make? I just use shell scripts for automation. The only case where you really need the incremental behavior of Make is C/C++ builds (and arguably it's increasingly inappropriate for this domain as well). For all other kinds of automation I just use shell scripts, since Make is mostly a horribly reinvented shell script dialect.
Saying that Make is a horribly implemented Shell dialect clearly seems like a misrepresentation of Make to me.
Make is a non-procedural way to describe the dependencies of your build process. You describe what you want as a result rather than the steps that the interpreter should follow.
It's possible to like or dislike this approach but it's clearly qualitatively different from Shell scripting.
Re: Grunt and RequireJS are out, it's all about Gulp and Browserify
#66This is a tangential question, but how do front-end people feel about the constant change in the field? I worked in the front-end and followed the trends for years and have found the changes difficult to follow. In 1997, the rage was VB and lots of cottage companies set up and advertising custom ActiveX widgets, on the web one had to learn ColdFusion and HTML/CSS. In early 2000's, VB6 was retired in favor of .net and…
> This is a tangential question, but how do front-end people feel about the constant change in the field?
I deliberately hang back on investing time in something unless it's immediately, drastically simpler than what's there now.
- My 47-line Gruntfile became a 23-line gulpfile, and I understood it better, so I learnt gulp.
- I don't see any huge advantage in using browserify, just syntactic difference, so I'm sticking to RequireJS right now.
- After reading about ractive and how simple it was (have an object, have a mustache template, you have bindings) I started using it in place of Angular.
Re: Grunt and RequireJS are out, it's all about Gulp and Browserify
#67This is a tangential question, but how do front-end people feel about the constant change in the field? I worked in the front-end and followed the trends for years and have found the changes difficult to follow. In 1997, the rage was VB and lots of cottage companies set up and advertising custom ActiveX widgets, on the web one had to learn ColdFusion and HTML/CSS. In early 2000's, VB6 was retired in favor of .net and…
> This is a tangential question, but how do front-end people feel about the constant change in the field? I deliberately hang back on investing time in something unless it's immediately, drastically simpler than what's there now. - My 47-line Gruntfile became a 23-line gulpfile, and I understood it better, so I learnt gulp. - I don't see any huge advantage in using browserify, just syntactic difference, so I'm sticki…
Speed is the reason. If you have gruntfiles that rely on a lot of compilation you know the pain of 5 or 6 second build times, with Gulp it's like a half a second.
Re: Grunt and RequireJS are out, it's all about Gulp and Browserify
#68what ! I just started using Grunt in a project .
on a side note: I realized some time ago that I really can't be using the latest thing always ( at least with JS ).
Re: Grunt and RequireJS are out, it's all about Gulp and Browserify
#69And again I'll remind people what happened in Java land: ANT -> Ivy/Maven -> Gradle I'll state it clearly: Grunt. is. Ant. It's a mess to follow a build script and a ritual to make it work in a real life project. I expected a tool like gulp to come sweeping in and it did, I'm extremely happy about that and started migrating away from the horrible tooling that is Grunt. I never understood how people can tolerate Grunt…
+1. I have spent more time reading about grunt than I have spent investigating + converting to + using gulp in production.
Re: Grunt and RequireJS are out, it's all about Gulp and Browserify
#70[deleted]