I'd wager this is largely due to how one is first exposed to agile methodologies. I'm young enough that I stumbled across agile as a way to solve problems, and so it sounds pretty good to me. However, my slightly older colleagues remember agile as the Newest Management Fad, with high priced consultants, seminars, certifications, and your boss paying lip service to change while still Not Getting It to match.
I like agile's philosophy, but I can certainly see lots of criticisms of Agile.
He created a startup for his pet project, eventually managed to get one customer for his product and then realised his idea was fundementally flawed and would never be commerically viable or even supportable.
That is still my impression of Agile - full speed ahead, buzzwords to maximum power and hope for the best.
Result: So now I'm doing the manager's job too.
I find it a waste of time, at least when implemented this way. The single bright spot: at least no more 2-hour rambling staff meetings!
Interestingly, the best development teams rarely display overt enthusiasm for their "methodology" and just get work done.
On my team we follow an agile approach, but we also have rough ideas on product direction for the next year or so and themed releases planned out for the next few months.
For us it all comes down to an understanding that if something else comes up then some of these features are going to have to slip to get other things in. It also means not building things that we ultimately aren't going to use.
If you just think that Agile means "don't plan, just do whatever you want" (i.e. Chaos) then of course you're going to hate it. No one can work like that.