3 ms·

You can write a replacement for gulp in Perl 6, but if it doesn't have the plugins, who will use it? Grunt and gulp have huge plugin ecosystems, which is both

• deniska 11y ago
  I personally like the idea of using good old Make for that task. You don't need "huge plugin ecosystem", you just need executables to use it. And unlike many other systems it does incremental builds without any special machinery.
  • DCoder 11y ago
    That's a valid approach, but "Good old Make" is only good if you are already familiar with it (and its quirks). If you're a new-ish web developer, "learning Make" and "learning Gulp" are two equally foreign tasks.
• Kabacaru 11y ago
  Also think of your target audience. All of them can program in JavaScript more or less, not all of them will want to learn Perl to do something they can do without learning a new language.
• deleted 11y ago
  [deleted]
• julianpye 11y ago
  How many of the plugins do you use and how many are overengineered for a simple purpose?
  • DCoder 11y ago
    In a fairly simple project, I have these: gulp-autoprefixer -- CSS vendor prefixes gulp-concat -- concatenates multiple files into one gulp-cssmin -- CSS minifier gulp-imagemin -- image optimizer/minifier gulp-rename -- renames files produced by other streams gulp-ruby-sass -- transpiles SASS to CSS gulp-template -- interpolates some variables, e.g. environment settings or external dependency URLs, into a file (basically lodash's .template ) gulp-typescript -- transpiles TypeScript to JS gulp-uglify -- JS minifier gulp-util -- provides things like access to environment variables, console.log replacement, Gulp-specific throwable errors gulp-watch -- automatically recompiles when source files change gulp.spritesmith -- converts images to CSS sprites