News for hackers. Stuff that matters.
Re:Ask HN: Why choose a dynamically typed language? by makmanalp on Saturday August 07, 2010 @02:20PM (#1584000)
I'm confused by your statement that statically typed languages are concise. Every time I program in Java, the code size ends up blowing up exponentially. However, a good 30-40% of the code is boilerplate rather than having to do with the task at hand. Now, this isn't a direct consequence of static typing BUT it looks like a very high portion of statically typed languages lean towards having a low content to code ratio.
Re:Ask HN: Why choose a dynamically typed language? by aristidb on Saturday August 07, 2010 @02:23PM (#1584007)
Java is not the only statically typed language, and some statically typed languages are almost phenomenally concise.
Re:Ask HN: Why choose a dynamically typed language? by makmanalp on Saturday August 07, 2010 @03:10PM (#1584098)
If you're referring to Haskell and the likes, sadly they're not nearly as prevalent.
Re:Ask HN: Why choose a dynamically typed language? by therockhead on Saturday August 07, 2010 @03:57PM (#1584184)
See Scala for a concise static typed language.
Re:Ask HN: Why choose a dynamically typed language? by whakojacko on Saturday August 07, 2010 @06:44PM (#1584488)
Or others. A lot of people seem to think of Java when they immediately think that static typed code has to be very verbose. Much of the verbosity of Java comes out of design decisions that were made by choice-Java does a lot to limit the programmer's power, for better or worse (Pretty much entirely worse when working with competent programmers)
Re:Ask HN: Why choose a dynamically typed language? by Rusky on Saturday August 07, 2010 @03:13PM (#1584109)
That is most definitely Java's fault for lacking good abstractions. Try Haskell or C#- much higher content:code.