4 ms·

Gulp and Grunt? Are you a time traveler from 2012?

jeroenhd 4y ago
Both still work fine to this day. I don't know what the exact (dis)advantages of the competing toolsets are, but if you know Gulp and Grunt then I don't see why you wouldn't use them.
- coredog64 4y ago
  Was helping an org migrate off of CloudFoundry and Grunt gave us no end of trouble. In the end, we wound up building with Node 8(!) and then praying that everything would still work with a 12.x runtime.
- andrew_ 4y ago
  unless one is in need of piping files (and streams) in a complex and prolific way, npm scripts or a makefile can supplant Gulp/Grunt with much less overhead.
ravenstine 4y ago
Yeah Grunt is pretty ancient but Gulp is still used in many places.
- Zardoz84 4y ago
  Gulp it's really useful when your workflow gets out of what webpack, esbuild & cia expects
azangru 4y ago
Look at the source code of web.dev site :-) It's Eleventy with gulp for asset management. https://github.com/GoogleChrome/web.dev https://github.com/GoogleChrome/web.dev
bluefirebrand 4y ago
I worked on a project using Gulp and Grunt as recently as 2020. This was a product the company I was working for inherited from a merger. They bought the company for this product. It was a nightmare of bad software practices. Still using Gulp in 2020 was only the tip of the iceberg.
- toomanybeersies 4y ago
  At least (I hope) you weren't still using Bower.
jitl 4y ago
¯\_(ツ)_/¯ used to build Typescript: https://github.com/microsoft/TypeScript/blob/main/Gulpfile.js https://github.com/microsoft/TypeScript/blob/main/Gulpfile.j...
- andrew_ 4y ago
  That is freaking bananas. Thanks for sharing.
aordano 4y ago
Gulp is practical to insert extra behavior if you have a multi-step build process and are allergic to Webpack. Just write a gulpfile and spawn whatever you need spawning, like some glorified bash that is already in JS so you don't need to manage more languages.
- deleted 4y ago
  [deleted]
theteapot 4y ago
2012 === bad. 2022 == awesome!

Both still work fine to this day. I don't know what the exact (dis)advantages of the competing toolsets are, but if you know Gulp and Grunt then I don't see why you wouldn't use them.

coredog64 4y ago
Was helping an org migrate off of CloudFoundry and Grunt gave us no end of trouble. In the end, we wound up building with Node 8(!) and then praying that everything would still work with a 12.x runtime.
andrew_ 4y ago
unless one is in need of piping files (and streams) in a complex and prolific way, npm scripts or a makefile can supplant Gulp/Grunt with much less overhead.

ravenstine 4y ago

Yeah Grunt is pretty ancient but Gulp is still used in many places.

Zardoz84 4y ago
Gulp it's really useful when your workflow gets out of what webpack, esbuild & cia expects

azangru 4y ago

Look at the source code of web.dev site :-) It's Eleventy with gulp for asset management. https://github.com/GoogleChrome/web.dev https://github.com/GoogleChrome/web.dev

bluefirebrand 4y ago

I worked on a project using Gulp and Grunt as recently as 2020. This was a product the company I was working for inherited from a merger. They bought the company for this product. It was a nightmare of bad software practices. Still using Gulp in 2020 was only the tip of the iceberg.

toomanybeersies 4y ago
At least (I hope) you weren't still using Bower.

jitl 4y ago

¯\_(ツ)_/¯ used to build Typescript: https://github.com/microsoft/TypeScript/blob/main/Gulpfile.js https://github.com/microsoft/TypeScript/blob/main/Gulpfile.j...

andrew_ 4y ago
That is freaking bananas. Thanks for sharing.

aordano 4y ago

Gulp is practical to insert extra behavior if you have a multi-step build process and are allergic to Webpack. Just write a gulpfile and spawn whatever you need spawning, like some glorified bash that is already in JS so you don't need to manage more languages.

deleted 4y ago
[deleted]

theteapot 4y ago

2012 === bad. 2022 == awesome!