I’m not certain who started the discussion and if it ever really mattered. I started to read this article at TechRepublic and I just could not get into it. I suppose that in the halls of academia there is need to have these sorts of confrontations but in the pragmatic world does it really make sense?For instance, I’m a programmer of some widget application. Within the application I have code that represents explicit and implicit contracts between objects, classes etc. And in the layer surrounding my widget I have some sort of abstraction or API layer. This layer defines a similar contract(s) between the widget (instance) and the widget’s users. Some of these contracts are defined in DOC and others in code and behavior. And when you get really nutty with inheritance static languages start to behave like dynamic ones.So what is the point of the post? The conversation is really about all of the other features and functions. The fact that we’re dwelling on “Static vs Dynamic” probably means that we do not have anything else to talk about or compare. I seriously doubt that this is going to be the make/break topic. “Static vs Dynamic” is getting an unreasonable amount of attention.Let’s move on to feature #2.