4 ms·
And 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 scrip
by jondot 13y ago
And 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. Long live gulp and common sense!.
- nailer 13y ago+1. I have spent more time reading about grunt than I have spent investigating + converting to + using gulp in production.
- brokenparser 13y agoI'd say Grunt is Maven because IDEs have no way to figure out beforehand what the build process will do.
- lmm 13y agoThat's the opposite of Maven. IDEs know exactly what a maven project will do (unless you're using plugins the IDE doesn't know about), because a maven build only does a very limited set of things (it mostly just compiles the source in src/main/java into target/). Which is what makes it great.
- tieTYT 13y agoI agree with you that "Grunt is ant". But when I look at that code example it seems like "Gulp is ant", too. It's just less verbose. I think that Lineman is the Maven equivalent in the JS world.