Home > Podcast > Episode 32 – Benefit of Dynamic Typing, PS3 Jailbreak, Verizon iPhone

Episode 32 – Benefit of Dynamic Typing, PS3 Jailbreak, Verizon iPhone

I caught a thread on the Scala-User mailing list recently where a person asked what the "Benefit of dynamic typing" was. Might be a bit of a one sided debate on a Scala list considering Scala is statically typed and you'd think its users would prefer the same. Turns out the Scala community comes from a fairly broad background, and there were some pretty good arguments put forth in favour of Dynamic Typing. What to know before debating type systems was a great link which popped up in the thread, highly recommend reading it.

In this episode we are simply kicking the tires around the topic of Dynamic vs. Static typing, in a future cast we'll try and give a go at debating the subject with people on both sides of the fence.

In other news George Hotz, who you may know if you've ever run blackra1n on your iPhone, felt the full force of Sony when he announced he discovered the key which allows you to sign your own software and run it on a Sony PS3. Because, you know, the PS3 your shelled out hundreds of dollars for obviously doesn't really belong to you, so you can't do with it as you please :S

And finally we talk about the Verizon iPhone and the possibility of a dual-mode (GSM/CDMA) iPhone 5 based on some discoveries made by iFixit.

Listen here:




About the Author

Craig Tataryn started his career as a Visual Basic programmer, but don't hold that against him! The system he helped create was a cutting edge, n-tiered revenue collection system whose transactions per second metric was off the charts! Around the year 2000 he discovered Struts and never looked back. A professional Java developer for close to a decade, Craig has worked on a wide variety of projects ranging from Recruiting, Purchase order, Revenue collection and Mortgage systems. More recently Craig has written web services for children's educational toys and has honed his skills on Wicket, SOA and iOS application development. "I love to learn and more importantly I love to teach. Hoarding knowledge is one of the most petty and selfish things you can do, especially as a contractor. This is why I always make it a point to document and share my knowledge with my client's employees"


  1. Troy Peterson
    February 13th, 2011 at 00:56 | #1

    Everyone may want to check out this talk by Randal Schwartz (Learning Perl, FLOSS Weekly). Slides and audio are both linked as “here” links on the post so please don’t miss them.

    Michael Galloy has a summary of his points.

  2. Guerry Semones
    February 16th, 2011 at 08:53 | #2

    Hey, I’m new here and really enjoying the podcasts! You’ve mentioned the code for buying “Programming in Scala 2nd Edition” a couple of times, but not mentioned where to code can be used. I tried Amazon and Artima. Sooo, what book site is it for? If there’s a link here I keep missing it.

  3. February 16th, 2011 at 09:00 | #3

    @Guerry Semones
    Thanks Guerry, there is a place in the checkout section of the shopping cart at the bottom to enter our code:


    Let us know if you have any trouble.

  4. Lee
    February 18th, 2011 at 13:52 | #4

    I disagree with the statement that assembly language was “strongly typed”. He said it was because there were only a couple of types.

    The way I see it, assembly is the ultimate untyped language. There is nothing in the assembler to determine whether you are putting 4 characters, two 16-bit signed integers or one 32 bit unsigned integer into a register. (On a machine with 32 bit registers.) You can copy a “pointer” (or address) into the middle of a string. You can treat part of a 60-bit floating point value as a pointer or even load it and jump to it as it were code.

    Most of these things I mentioned above are bad(tm) things to do though I can think of a few funky things where you treat the bits as one type to speed up working with them.

    Or look at it from the point of “run time” vs “compile time”. In assembly, nothing much is checked at compile/assemble time but the failures happen at runtime whether they generate a true error or just go on running and doing unintersting things.

  1. February 11th, 2011 at 12:11 | #1
  2. February 14th, 2011 at 12:54 | #2
Support Wikipedia