Post History

If it were always better to use `static`, the language would have been designed to always assume `static`, or at least default to `static`. That the language defaults to making methods not static indicates that the designers of the programming language envisioned static methods to be rare.

Java is indented to be an object oriented programming language, where a program is a set of objects that "talk" to each other using methods. Objects are created from classes, and classes can be related through inheritance. Specifically, a class can be declared to extend another class, which allows it to inherit or override methods from the parent class. For instance:

    class Animal {
       void move() {
           System.out.prinln(this + " moves");
       }
    }

    class Dog {
       @Override
       void move() {
           System.out.println("The dog walks");
       }
    }

    class Snake {
       @Override
       void move() {
           System.out.println("The snake slithers");
       }
    }

Which you can then use as follows:

    Animal animal = new Snake();
    animal.move(); // "The snake slithers"

So even though the variable contains an `Animal`, that `Animal` knows whether it is a `Dog` or a `Snake`, and responds accordingly when it is asked to `move`. 

This ability to refine the behavior of a class in a subclass is very useful. However, since this depends on the type of the object, it is only available for methods of objects, not static methods.

By using static, you deny yourself this useful tool. This may seem a small price to pay when your programs are tiny and consist only of a few isolated methods. However, once your programs get bigger, and particularly once they start incorporating code written by other people, the ability to refine code they have written will be invaluable.