3 ms·
That might be true at the start of the project. But to be honest, having worked quite a few years with strong type systems, weak type systems and dynamic type s
by gordaco 9y ago
That might be true at the start of the project. But to be honest, having worked quite a few years with strong type systems, weak type systems and dynamic type systems, I've found that not having a strong type system is precisely what makes work grow faster than expected. Maybe it's because I'm accustomed to big projects, but I've been bitten too many times. I'd even choose Java over any language that doesn't have a dependable type system.
- pmoriarty 9y ago"having worked quite a few years with strong type systems, weak type systems and dynamic type systems" Sorry to be pedantic, but you probably mean static type systems, not strong type systems. See: "What to know before debating type systems" - http://blogs.perl.org/users/ovid/2010/08/what-to-know-before-debating-type-systems.html http://blogs.perl.org/users/ovid/2010/08/what-to-know-before...