On Wed, Oct 12, 2011 at 3:01 PM, phil swenson <[email protected]> wrote: > > >> I'm still puzzled by Dart's allowance of dynamic typing, though. What's >> the rational here? Saving a few keystrokes just so you can prototype faster? >> This doesn't make much sense. > > this is what I think you don't get: most web devs like dynamic typing.
I think people just like it when things work as well as they can. When building a bike, you are likely to try riding it a few times before it is really "ride-able." With what is commonly called dynamic typing, you can typically do this. With static typing, if it won't stand, it won't run. Period. In this regard, I admit I would like an optionally static/dynamic split. Imagine testing a few additions to a visitor/node tree where you purposefully didn't completely all implementations of the methods because you just aren't there yet and don't care. (If you have several visitors, might want to just try one or two at a time, for example.) This is certainly doable with a lot of upfront planning regarding modular codebases, but it would be a lot easier if you could just say "don't enforce this now." Obviously, this is all starting with "I think." So, your mileage will vary. I'm interested in how far off the mark I am, though. -- You received this message because you are subscribed to the Google Groups "The Java Posse" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/javaposse?hl=en.
