Well, it might be more accurate to say it was written with the influence of everything. The object system borrows liberally from smalltalk, much of the other new features are influenced by Haskell, and it's all wrapped up in a Perlish way of looking at programming.
In short, if you hate how Perl 5 allows for multiple ways to accomplish something and think it's a big mess, I imagine you might find more to dislike in Perl 6. If you like power, flexibility, sane defaults for the common case, and lots of features, Perl 6 will be a wonderful place.
Then again, I'm of the opinion that a large percentage of people that think they dislike Perl 5 as an unorganized mess are actually laboring under a false partial impression. Perl is actually highly organized on core principles, it's just that those principles are far more radically different than the familiar syntax implies. Approaching Perl from a procedural C-style background and expecting the same will mostly work, but there will be aggravating times where you just don't understand why certain design choices were made that continually cause friction.
In short, if you hate how Perl 5 allows for multiple ways to accomplish something and think it's a big mess, I imagine you might find more to dislike in Perl 6. If you like power, flexibility, sane defaults for the common case, and lots of features, Perl 6 will be a wonderful place.
Then again, I'm of the opinion that a large percentage of people that think they dislike Perl 5 as an unorganized mess are actually laboring under a false partial impression. Perl is actually highly organized on core principles, it's just that those principles are far more radically different than the familiar syntax implies. Approaching Perl from a procedural C-style background and expecting the same will mostly work, but there will be aggravating times where you just don't understand why certain design choices were made that continually cause friction.