Posted By: Glucose | Oct 23rd @ 12:46 AM | 39,499 Views | 10 Comments
I spoke at the StackOverflow conference in San Francisco and Seattle this week (long week, let me tell you) and I got the opportunity to sit down with Jeff Atwood from CodingHorror and Joel Spolsky from Joel on Software, along with the man, the legend, Rory Blyth. The audio also appeared on the StackOverflow podcast in part, but here's the raw video from our backstage ramblings.
Warning: extreme ramblosity ahead!
  • Joel explains his Duct Tape Programmer post. Apparently DevDays is a duct tape conference, and this section of the recording is a duct tape podcast.
  • Some discussion of the ubiquity of mobile code. Also, if you are nostalgic for the era “when development was hard”, the consensus is that you should be doing mobile development today on iPhone, Android, Windows Mobile, or Symbian.
  • Rory elaborates on his experience with (and effusive opinions on) iPhone development to date. Is coding in Objective-C best accompanied by a flux capacitor, New Coke, and Max Headroom? Also, his excitement for MonoTouch.
  • Joel and Scott put on their amateur language designer hats and have a spirited discussion of type inference and Fog Creek’s in-house DSL, Wasabi.
  • Scott covers some of the highlights of new and shiny features coming in the Visual Studio 2010 IDE, the C# 4.0 language, and the ASP.NET MVC 2.0 web framework.
Rating:
2
2

Could somebody please confirm or deny the rumor that, that is in fact, Rory Blyth picking his nose in the mirror?

It's strange how discussions with apparently no content or direction turn out to be one of the most entertaining ones.

Well, the sound on my MacBook is really quit :/

Richard.Hein
Richard.Hein
... my guitar gently weeps ...

Joel is right about type inference for parameters.  F# does it.  From the docs:

 

Inference of Parameter and Return Types

In a parameter list, you do not have to specify the type of each parameter. And yet, F# is a statically typed language, and therefore every value and expression has a definite type at compile time. For those types that you do not specify explicitly, the compiler infers the type based on the context. If the type is not otherwise specified, it is inferred to be generic. If the code uses a value inconsistently, in such a way that there is no single inferred type that satisfies all the uses of a value, the compiler reports an error.

The return type of a function is determined by the type of the last expression in the function.

For example, in the following code, the parameter types a and b and the return type are all inferred to be int because the literal 100 is of type int.

let f a b = a + b + 100

There is parameter type inference in C# now guys, circa .NET 3.x.  It's a generic method/function (it has to be static I think).  LINQ does it all the time, take a look at the Aggerate<> method it's an extension method (function) as one example on the IEnumerable<> type, all the parameters are infered.

Selling points for .NET 4.0,

  1. variance, (proper co-/and invariance).
  2. Visual Studio improvments (not part of .NET 4.0 but unquestionably so, !important)
  3. DLR...

(the DLR is actually, not so much of a .NET 4.0 thing though, my list would actually only include one thing, and that's the new variance features built into the new C# compiler).

 

With all the stuff, F#, M, Iron... and new language features the .NET 4.0 release is a big one.

This was awesome, thanks for sharing. I actually prefer these kind of free discussions, I find them at least as informative / helpful in helping me think about programming as "targetted" content.

My Peace Corps host father, Mauritania 2003, asked to see my cellphone. You know, Americans have all the latest tech. I had recently bought the latest Ericsson in America. When he saw it, he looked disappointed and pulled out ... the same model. They were relatively prosperous. He had 12 goats and a delapidated delivery van. When the van hit a camel, he became destitute.

Microsoft Communities