> Programming usually goes down two routes: > > 1) the problem at hand is trivial. In this case, a static > type system won't help because the problem is trivial. > > 2) the problem at hand is quite complex. In this case, a > static type won't help as well, because the code will > usually involve lots of subclasses and interfaces.
Oh, that sounds like fun. Let me try!
1) The problem at hand is trivial. In this case, you won't have that many types since the program is trivial, so a statically typed language doesn't have any overhead and is safer.
2) The problem at hand is quite complex. In this case, you need types even more because the code will involve lots of subclasses and interfaces.
Previous Topic
