First, all language decisions are decisions made by the language creators. There is nothing in the world of software engineering or language defining or compiler / interpreter writing which says that a static method cannot be part of an interface. I've created a couple of languages and written compilers for them -- it's all just sitting down and defining meaningful semantics. I'd argue that the semantics of a static method in an interface are remarkably clear -- even if the compiler has to defer resolution of the method to run-time.

其次，我们使用静态方法意味着有一个包含静态方法的接口模式的正当理由——我不能代表你们，但我经常使用静态方法。

The most likely correct answer is that there was no perceived need, at the time the language was defined, for static methods in interfaces. Java has grown a lot over the years and this is an item that has apparently gained some interest. That it was looked at for Java 7 indicates that its risen to a level of interest that might result in a language change. I, for one, will be happy when I no longer have to instantiate an object just so I can call my non-static getter method to access a static variable in a subclass instance ...

静态方法不像实例方法那样是虚拟的，所以我猜想Java设计者决定不让它们出现在接口中。

但是您可以将包含静态方法的类放在接口中。你可以试试!

public interface Test {
    static class Inner {
        public static Object get() {
            return 0;
        }
    }
}

让我们假设在接口中允许使用静态方法: *它们将强制所有实现类声明该方法。 *接口通常是通过对象来使用的，所以唯一有效的方法是非静态方法。 *任何知道特定接口的类都可以调用它的静态方法。因此，实现类的静态方法将在下面被调用，但调用方类不知道是哪个。怎么知道呢?它没有实例化来猜测!

接口被认为是在处理对象时使用的。这样，对象就从一个特定的类实例化了，所以最后一个问题就解决了。调用类不需要知道具体是哪个类，因为实例化可能由第三个类完成。因此调用类只知道接口。

If we want this to be extended to static methods, we should have the possibility to especify an implementing class before, then pass a reference to the invoking class. This could use the class through the static methods in the interface. But what is the differente between this reference and an object? We just need an object representing what it was the class. Now, the object represents the old class, and could implement a new interface including the old static methods - those are now non-static.

元类就是为此目的服务的。你可以试试Java的class。但问题是Java在这方面不够灵活。不能在接口的类对象中声明方法。

这是一个元问题-当你需要做屁股

．．等等等等

不管怎样，你有一个简单的解决方法——用相同的逻辑使方法非静态。但是，您必须首先创建一个对象来调用该方法。

可以实现的是静态接口(而不是接口中的静态方法)。实现给定静态接口的所有类都应该实现相应的静态方法。你可以从任何Class clazz中获得静态接口SI

SI si = clazz.getStatic(SI.class); // null if clazz doesn't implement SI
// alternatively if the class is known at compile time
SI si = Someclass.static.SI; // either compiler errror or not null

然后你可以调用si.method(params)。 这将很有用(例如对于工厂设计模式)，因为您可以从编译时未知类获得(或检查)SI静态方法实现! 动态分派是必要的，您可以通过扩展类(当通过静态接口调用时)来重写类的静态方法(如果不是final方法)。 显然，这些方法只能访问它们类的静态变量。

接口只是提供一个类将提供的东西的列表，而不是这些东西的实际实现，这就是你的静态项。

如果你想要静态，使用一个抽象类并继承它，否则，删除静态。

希望有帮助!

假设你能做到;想想这个例子:

interface Iface {
  public static void thisIsTheMethod();
}

class A implements Iface {

  public static void thisIsTheMethod(){
    system.out.print("I'm class A");
  }

}

class B extends Class A {

  public static void thisIsTheMethod(){
    System.out.print("I'm class B");
  } 
}

SomeClass {

  void doStuff(Iface face) {
    IFace.thisIsTheMethod();
    // now what would/could/should happen here.
  }

}