IMO, this is one of the major issue of javascript.
The specified classes for arguments is a good thing since you dont have to dig through piles of documentation or code review every method you use to understand their behavior.
What do you expect the arguments of the following function to be: 1. A file descriptor, or 2. A path to a file that will be opened by the function?
def print_log(file): ...
One could argue it's bad naming convention but i see shit like this way too often to think it can be solved by conventions. Documenting doesn't work either for the same reason, documentation becomes more boilerplate than specifying types in a type safe language btw.
Contrast this with the C# equivalent
void PrintLog(File file) { ... }
Bang!, You instantly know that the file parameter is a File-object and you can focus your mind on more important things.
IMO, real advantages of dynamic typing vs static typing are
* Simplicity. You don't need to learn a complex type system to start coding.
* Flexibility. Dynamic type systems don't stop you from doing useful things ike polymorphism and generics. In a static type system those need to be build in from day 1.
And having to build more advanced type system features on top of a simpler type system is hardly a good thing either - type theory is not trivial and chances that you will get it wrong are large. Even experts in the field make wrong decisions, for example array covariance in Java an C#. And even if you get it right you will usually not enjoy (all) the benefits of compile time type checking and fail only at runtime.
It felt like even the implementers of those type-systems didn't get it right.
I've never used Smalltalk, but the other two you mention suffer from massive problems when you get to a certain size codebase.
I'm extremely wary of saying this, but I generally think that uni professors/tutors can't program. Basically unless they've written a large open source program or actually worked in the industry for a lot of years, they're probably going to be useless programmers. And even then, there's a good chance they're useless programmers.
That may be a slightly old fashioned view, but most lectures I've seen from unis online tend to completely miss the point of basic concepts (OO being the most common one). And it's rare to meet graduate CS who can actually program anything on their own from scratch. Google's fine, but cut & pasting code you don't understand and changing random stuff as it sounds kinda right, that's not programming, that's a bloody rain dance.
Programming is a skill that needs years of work before you're even vaguely good. And the worst part is you're almost constantly suffering from the Dunning-Kruger effect, thinking you're much, much better than you actually are. I probably still am.
It's one of the reasons we see security holes time and time again, novices don't even realise the problem exists!
For example, I have no idea what to do with crash dump in windbg. I wouldn't even know where to start. Is that a massive knowledge gap? But give me a stack trace of a problem & the source in almost any web language and I'd probably be able to fix it, even if I've never used the programming language before.
But I have to say, my programming prof. was rather fond of Java. Biggest part of the lecture on OOP was about type systems (and I hated it lol).
Most of the stuff I learned about programming, I didn't learn in university, but at work.
But since my experience with Java at university was so bad, I searched for jobs in different languages, like JavaScript.
A few years ago I tried to learn Scala, because it seemed like a better Java to me. But somehow I never got along with it. The type-system seemed logical, but it had so much other stuff around that made starting rather difficult, so I went back to JavaScript.
When using libraries, their functions always wanted their arguments to be some strange classes or implement some of their interfaces, which always seemed like big overhead to me.
Stuff like Smalltalk, PHP and JavaScript felt much faster in development speed.