5 ms·

this, let's implement inheritance movement nonsense is crufts of Java and C++. (and only C++ can be forgiven, for performance reasons.) Python has proven that

this, let's implement inheritance movement nonsense is crufts of Java and C++. (and only C++ can be forgiven, for performance reasons.) Python has proven that a successful dynamic language should have duck-typing, via what called late-binding. you perform lookups on a live object. And this makes even more sense for javascript, which intentionally violates whole notion of typing. In python, yes, there are such things like 'abstract base classes', but they're mostly for convenience, not forced like interfaces in Java. which means no one write codes like: If not isinstance(obj, JavaicMentalMasturbationBase): raise TypeError, "rogue object does not follow holy Javaland commandments: %r" %obj instead, they exist that a framework provider can tell developers, on what are the possible objects that can be fed to their framework. e.g) to use our SessionInterface, your custom session has to provide get_session and save_sesion methods. It seems like Branden Eich's original intention has came to fruition - create a sub-par language and name it after Java. sub-sub-par developers from Java will like the language, it even has closures! But I think he didn't expected Java idiots to force their idioms and harm the whole ecosystem - usually, enterprisey code monkeys were very silent in their cubicles.

stcredzero 13y ago
Python has proven that a successful dynamic language should have duck-typing, via what called late-binding. "Python did that?" asks the Smalltalker.
coldtea 13y ago
>Python has proven that a successful dynamic language should have duck-typing, via what called late-binding. You perform lookups on a live object. It has proven nothing of the short. For one, other languages have done it before (and much better, like Smalltalk). Second, it's not something that, in Python's implementation, makes it particularly suited or pleasant for large codebases. >e.g) to use our SessionInterface, your custom session has to provide get_session and save_sesion methods. So, relegate work that the computer can do to the programmer. Make him do tedious and error-prone housekeeping. The rest of the comment reads like a teenager's attempt at sounding like "cool" and in the know. Things line "JavaicMentalMasturbationBase", "create a sub-par language and name it after Java", "Java idiots" and the like. I assure you that there are Java developers who run circles around whatever your coding skills are. And from your description you don't sound that good at Python either.

stcredzero 13y ago

Python has proven that a successful dynamic language should have duck-typing, via what called late-binding. "Python did that?" asks the Smalltalker.

coldtea 13y ago

>Python has proven that a successful dynamic language should have duck-typing, via what called late-binding. You perform lookups on a live object. It has proven nothing of the short. For one, other languages have done it before (and much better, like Smalltalk). Second, it's not something that, in Python's implementation, makes it particularly suited or pleasant for large codebases. >e.g) to use our SessionInterface, your custom session has to provide get_session and save_sesion methods. So, relegate work that the computer can do to the programmer. Make him do tedious and error-prone housekeeping. The rest of the comment reads like a teenager's attempt at sounding like "cool" and in the know. Things line "JavaicMentalMasturbationBase", "create a sub-par language and name it after Java", "Java idiots" and the like. I assure you that there are Java developers who run circles around whatever your coding skills are. And from your description you don't sound that good at Python either.