I believe object-oriented design and programming specifically around C++ became mis-used, despite the warnings from the luminaries who were writing books and training, when C++ first came out.

I think some of the concepts are getting out of hand, like object functional programming.

I’ve been playing recently with Ruby and Javascript (NodeJS), and each day more I more tedious of working with Java.

Interesting discussion.

Yeah I didn’t taste (for real production code) any other static typed language ;( so my judgment it’s limited to C# and Java.

In fact, now I counted that I used more dynamic languages than static.

I coded some playground apps using Scala and Haskell and my feeling weren’t very fine, maybe I didn’t get the required experience or give them the needed time, like I did with Clojure.

Anyway, thanks I’ll give a look on golang.

The advantages of static typing include, obviously, safety: they give you an extra layer of tests that ensure at compile time that your values (objects or not) are being used correctly. Whether that’s really that useful depends on the application – certainly more critical software can use all the verification possible.

But I think you should hold your judgment until you’ve used languages besides early C#/Java which are criticized even by static typing fans.

Type inference, structural typing, static duck typing are features of type systems present in other languages (Haskell, OCaml, etc).

Personally, I like Go: it gives you the ‘feel’ of a dynamic language while ensure plenty of static safety.