Modern IDEs make that whole thing moot anyway, but the notation is still being used afaik.
There is nothing wrong with type-safety per se, it's just that when it gets to the point where it is literally 'in the way of progress' that things have been taken too far.
Ideally its something that's there when you need it, and override-able when you specifically don't need it.
That way you can do your type checking at compile time for the 70% or so of the code where that makes good sense, and where you're happy to have those guardrails to save you some time catching stupid bugs.
The other 30% of your code you can be as free as you want to be knowing full well that the price of failure would be a very angry end user.
That's because I think there are multiple 'modes' of programming, if you're writing a one-off data import script then type safety is just a real pain, as soon as you want to do that every day at a few thousand locations you'd better have it bullet proof.
Now you need two languages for those two situations.
The risk is that I unfairly maligned Java, a language which I do not know well anymore, since I abandoned it about when it started to look like this. But according to you I'm being too generous to them as well. :)
that was true only up to about C# 2.0; Java is way, way behind nowadays.
No, because C# had generics before Java.
I wonder sometimes if the same thing has happened to type safety. I'm not convinced it is a bad idea, actually. I am convinced that it's not well-served by having Java as it's poster child. If my mental picture of a type-safe language is something that reads like this, no wonder I'm inclined to think it's overrated.