4 ms·

> my newer projects just use scripts now to do building and I just simply reference the same depdencies grunt and all wrap Which is basically reinventing the w

by petetnt 11y ago

> my newer projects just use scripts now to do building and I just simply reference the same depdencies grunt and all wrap Which is basically reinventing the wheel for the Xth time, but now with your spin on it. Don't get me wrong, I have nothing against spinning a script or two for building, but as soon as you share them with others there might be some problems. Modern build systems have pretty thriving ecosystems which means less time doing stuff which is out of the development time. Thriving ecosystems mean that many are already familiar with the tools, which means less time for them to get a grasp of your project. And so on and so on. There are many benefits of using commonly used tools besides just running few simple or complex scripts.

BinaryIdiot 11y ago
> Which is basically reinventing the wheel for the Xth time, but now with your spin on it. False. Do you consider calling a function versus setting a property, even if they use the same amount of lines of code, reinventing the wheel? I sure don't. It didn't take long at all for me to write and npm already provides a way to run scripts so I can still do `npm run build`, etc just as if I typed `grunt build`. > Modern build systems have pretty thriving ecosystems which means less time doing stuff which is out of the development time. Thriving ecosystems mean that many are already familiar with the tools, which means less time for them to get a grasp of your project. And so on and so on. There are many benefits of using commonly used tools besides just running few simple or complex scripts. The vast, vast, vast majority of Grunt and Gulp plug-ins simply wrap existing libraries, make a call to those libraries with the options you define in Grunt or Gulp and then move to the next step when it's finished. That's it. When I moved a web app from Grunt to my own script, that still used the same dependencies, the amount of code was almost the same minus all the grunt dependencies.

by petetnt 11y ago

BinaryIdiot 11y ago

> Which is basically reinventing the wheel for the Xth time, but now with your spin on it. False. Do you consider calling a function versus setting a property, even if they use the same amount of lines of code, reinventing the wheel? I sure don't. It didn't take long at all for me to write and npm already provides a way to run scripts so I can still do `npm run build`, etc just as if I typed `grunt build`. > Modern build systems have pretty thriving ecosystems which means less time doing stuff which is out of the development time. Thriving ecosystems mean that many are already familiar with the tools, which means less time for them to get a grasp of your project. And so on and so on. There are many benefits of using commonly used tools besides just running few simple or complex scripts. The vast, vast, vast majority of Grunt and Gulp plug-ins simply wrap existing libraries, make a call to those libraries with the options you define in Grunt or Gulp and then move to the next step when it's finished. That's it. When I moved a web app from Grunt to my own script, that still used the same dependencies, the amount of code was almost the same minus all the grunt dependencies.