What's wrong with static methods?

Question

Answers on an postcard please.

Answer 1

I think the point here is that sometimes people come from a procedural background (or maybe no background) and they start with main, and one static method leads to another. They reach a tipping point where they are reluctant to define non-static methods to a class because it's all static elsewhere. And static method can't access instance data, so their data becomes largely static as well. When the dust settles, they are programming procedually in Java. So too many static methods is a sign that you may be programming procedurally instead of doing OOP, but using static appropriately is still cool.
And let's not get pedantic. What goes wrong if I make my String class's getLength method static?
public final class MyString {
    private int length;
    public static int getLength(String s) {
        return s.length;
}It's a misuse of static, but it doesn't break my design.