For me it is a mix of zillions of libraries with broken package management (npm + gulp). Compare to maven in java. Yes, you need to write XML, but it is not th

For me it is a mix of zillions of libraries with broken package management (npm + gulp). Compare to maven in java. Yes, you need to write XML, but it is not that hard, you mostly add <dependency>. And then it just works. And with npm, I get - this doesn't work with that version of npm (which BTW has a funny versioning that is almost exponential, there are 0.x and x.x versions), but it doesn't say that the version is wrong, it just does not work and you are to figure out why. More over, npm package locations, you can have three places, in project directory, in home directory and system wide. And to make matters worse you switch between those by using a command line switch. And it breaks, because once you downloaded a package into home dir (accident) and then your packages in current dir don't work, just because - build breaks and you are out of luck. I don't even count how many times I had to remove all npm directories to get rid of some package that was downloaded. With maven you have simple system, that is constraint and because of that you have much fewer places where it will shoot you in the foot. With npm (+gulp) you get wild west of package management, just like it was with ant days of java. And don't get me started on the AngularJS - I thought that I won't see anything that complicated since the days of EJB < 3.