Type Safety in a Loosely Coupled World. In which I'm inspired by Tim Ewald and come to realize that runtime type checking is a very good thing. [sellsbrothers.com: Windows Developer News]
There seems to be a lot of developers moving towards using untyped languages, or untyped constructions in typed languages.
The main argument is that the reason you want type safety is to make the compiler find your errors. The (high) price you pay for that is lack of flexiblity. If you have a good test suite, which you should have anyway, you can use it to check your errors, while being able to take advantage of the flexiblity of untyped constructions.
I like the idea ...
5:19:18 PM 
|
