Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Grunt 1.0.0 released

gruntjs.com

Post reply on HN
Print view View original

81–90 of 106 posts

Re: Grunt 1.0.0 released

#81

Post by Ciantic »

nailer wrote: post #74
pcr0 wrote: post #43

Earlier quoted context omitted.

Where does it say it uses script tags for input? The quote you mention says CommonJS/AMD. CommonJS is the de-facto standard these days. Typically, people write in ES6 imports, which then gets transpiled to CommonJS anyway. It accepts AMD as an option, but honestly, I've been using webpack for about a month and I haven't come across a single library that recommends using AMD. It's just there as an option for those who…

You admit most of the world had moved on from AMD, but don't see why advertising AMD support as a main feature - to the point it's mentioned in the sites description - would dissuade people? Being able to shim script tag libraries is mentioned in various places through the docs (and used to be even more prominent than it is now). I'm responding out of charity here: you made an angry response, were shown to have misre…

Mr. that was not my reply, and I didn't made a angry response... If you thought my characters conveyed angryness I apologize, I just critcized your points.

Re: Grunt 1.0.0 released

#82

Post by johnieeboy »

rkwz wrote: post #31
igl wrote: post #9

Obsolete before it hit 1.0. While grunt/gulp was fun for a while... i am not looking back to our 800 line grunt file, complicated async configuration and the tons of dev-dependencies. Webpack blew everything out of the water. 80 lines of config, hot-reloading, code-spliting, hash-filenames... Looking forward to whats coming next.

The problem with Webpack is that if you want to do something that's not straightforward[1] or covered in the dozen tutorials that are on the web, you're going to have a hard time. The docs are very basic and there are so many configuration params. If you want to do something that's not covered in tutorials or boilerplates, be prepared to spend a ridiculous amount of time reading Webpack PRs, issues and the codebase.…

Funny enough, if you look at the comments for pretty much the landing page of web pack you get the same sentiment

http://webpack.github.io/docs/what-is-webpack.html

Re: Grunt 1.0.0 released

#83

Post by biot »

splintercell wrote: post #67
uhtred wrote: post #46

Earlier quoted context omitted.

Holy crap! I left a company 6 months ago and we were using Gulp there, and it was, as far as I am aware, the hot thing to use (I'm no front-end dev). Now you're telling me it is obsolete?! Javascript world is silly.

I am sorry but if someone told me that the product which came out yesterday is obsolete then I'd understand that Javascript world is silly, but if at your company a product which was popular 3 years ago cool, then it's your company's fault.

Javascript was popular 3 years ago. What new, cool thing have you moved on to?

Re: Grunt 1.0.0 released

#85

Post by rhinoceraptor »

rkwz wrote: post #31
igl wrote: post #9

Obsolete before it hit 1.0. While grunt/gulp was fun for a while... i am not looking back to our 800 line grunt file, complicated async configuration and the tons of dev-dependencies. Webpack blew everything out of the water. 80 lines of config, hot-reloading, code-spliting, hash-filenames... Looking forward to whats coming next.

The problem with Webpack is that if you want to do something that's not straightforward[1] or covered in the dozen tutorials that are on the web, you're going to have a hard time. The docs are very basic and there are so many configuration params. If you want to do something that's not covered in tutorials or boilerplates, be prepared to spend a ridiculous amount of time reading Webpack PRs, issues and the codebase.…

I could not for the life of me get Webpack to bundle '.json' files that were require()d by some library code I was using. Of course, this functionality comes out of the box with Browserify.

Re: Grunt 1.0.0 released

#86

Post by [deleted] »

vladikoff wrote: post #48

Hey! Core maintainer here. I see a lot of comments are basically saying our project is obsolete or sucks. That does not stop us from working on Grunt though. We are still seeing record download numbers, even with the 2 year old releases. This is why we felt it was important to keep releasing this software and supporting developers. For those who support and use Grunt - huge thank you! Pick up your free open-source co…

[deleted]

Re: Grunt 1.0.0 released

#87

Post by BinaryIdiot »

petetnt wrote: post #69
BinaryIdiot wrote: post #54

Earlier quoted context omitted.

Honestly there isn't much point. You can do the same stuff on grunt, gulp and apparently webpak. Personally, to avoid the extra mountain of dependencies, my newer projects just use scripts now to do building and I just simply reference the same depdencies grunt and all wrap. It's quite easy. Honestly there is some utility to using these build systems as they make it a tiny bit easier than just writing a script...but…

> 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 w…

> 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.

Re: Grunt 1.0.0 released

#88

Post by skeeterbug »

vladikoff wrote: post #48

Hey! Core maintainer here. I see a lot of comments are basically saying our project is obsolete or sucks. That does not stop us from working on Grunt though. We are still seeing record download numbers, even with the 2 year old releases. This is why we felt it was important to keep releasing this software and supporting developers. For those who support and use Grunt - huge thank you! Pick up your free open-source co…

Thanks a lot for your hard work and keeping the project stable. The Infor CRM mobile team added grunt to our project back in July of 2013. I have probably written about a dozen plugins and custom tasks internally. The plugin API docs are a great resource. I love the configuration first approach with the ability to fall back to code if needed. It has really treated us well.

I also gave a presentation at our partner conference a year and a half ago on using grunt for development. Keep up the great work!

Re: Grunt 1.0.0 released

#89

Post by armandososa »

reitanqild wrote: post #70
vladikoff wrote: post #48

Hey! Core maintainer here. I see a lot of comments are basically saying our project is obsolete or sucks. That does not stop us from working on Grunt though. We are still seeing record download numbers, even with the 2 year old releases. This is why we felt it was important to keep releasing this software and supporting developers. For those who support and use Grunt - huge thank you! Pick up your free open-source co…

I don't get node and npm (although I was good with JS), but you seem to be cool. Noted. : ) Edit: again, now that we have a bunch of people capable of understanding trendy JS here: Care to share a link to somewhere I can learn?

Here: http://blog.keithcirkel.co.uk/how-to-use-npm-as-a-build-tool...

I don't hate grunt, I used to love it and used it for all my projects. And then I started using gulp.

But after reading this article I just use npm script 99% of the time. I don't know if it is better over all, I just prefer it over grunt/gulp.

Re: Grunt 1.0.0 released

#90

Post by thegayngler »

vladikoff wrote: post #48

Hey! Core maintainer here. I see a lot of comments are basically saying our project is obsolete or sucks. That does not stop us from working on Grunt though. We are still seeing record download numbers, even with the 2 year old releases. This is why we felt it was important to keep releasing this software and supporting developers. For those who support and use Grunt - huge thank you! Pick up your free open-source co…

Thank you so much! I appreciate all the work you've put into Grunt even though I personally prefer Webpack, configuration, HotModuleReloading and I've been able to make it work with webcomponents and reactjs. At work we use Grunt so maybe this will help me at work but I am actively trying to convince my team to switch to Webpack.
Post reply on HN