News for hackers. Stuff that matters.
Re:Ask HN: Why choose a dynamically typed language? by seasoup on Saturday August 07, 2010 @07:40PM (#1584575)
Working with static types feels like wrestling the code around. Why should the programmer have to care about internal dynamics of a language that are the difference between double, long, int, Integer, Long, short, etc. The compiler or run-time environment should figure it out. That's one more thing that can break, that I'll have to fix.

It gets really irritating when it's an attribute of an object that's returned by a getter that's wrong and cannot be cast, then I need to figure out if this thing is used anywhere other then the place I'm at and if it is, create a new method or... at this point the code is just getting in my way.

Re:Ask HN: Why choose a dynamically typed language? by gaius on Sunday August 08, 2010 @05:51AM (#1585130)
Yeah, that type (heh) of typing is boring. What is really, really useful, tho', is a type system that can stop you doing things that make no sense in your problem domain. This was the original idea behind Hungarian notation btw: the C compiler can trap things like multiplying a char by a double; it can't trap you adding a weight to a height.
Re:Ask HN: Why choose a dynamically typed language? by seasoup on Tuesday August 10, 2010 @02:43PM (#1592535)
Would be nice to have a mixed dynamic/static typing system. So you can static type when you need the solidity and dynamic type when you want ease of use.