Herding Code

View Top 200 Chart

Back to Rankings Page

News
**Herding Code**

A technology podcast with Jon Galloway, Scott Allen, Kevin Dente, Scott Koon

Latest Episodes:

**Herding Code 106: Mark Rendle on Simple.Data** Feb 22, 2011
Show notes

**Episode 106**

In this episode of Herding Code, the guys speak with Mark Rendle about his Simple.Data and Fix projects.

The show begins with Mark's Simple.Data elevator pitch in which he explains that Simple.Data is an ORM without the O, the R or the M.

Jon asks about Mark's heavy use of dynamic types in the Simple.Data source. Mark talks about the Method Missing pattern in Ruby and how that translates to dynamic .NET programming in Simple.Data.

Jon and Mark dig deeper into the code and then they walkthrough project advancement from supporting basic CRUD functions to the recent addition of database transactions.

Mark shares Simple.Data's current and future support for numerous relational and non-relational databases.

Jon and Mark talk about the use of MEF, rather than a full-blown IoC container, in Simple.Data.

Scott K and Mark discuss Simple.Data tests, their implementation and the TDD and FDD (Fear-driven development) which Mark took while developing his project.

Kevin asks if the heavy use of dynamics instigated the need to write more tests. Mark answers by sharing his views on why coders might prefer either static or dynamic typed languages.

Jon asks about Simple.Data adoption and code optimizations which might be required to support increased production use.

Mark digs into Reactive Extensions and how it's used in Simple.Data.

Mark talks about the growing movement of simple web development projects and the tools/frameworks which support these efforts and, coincidently, answers @AaronOnTheWeb's Twitter-submitted question.

@CodeReflection asks about Simple.Data support for aggregates which prompts a discussion about where/how these operations should be handled.

@jacksonh asks about support for asynchronous operations.

The conversation switches to Mark's involvement with OWIN and his Crack Fix project offers an ultra-lightweight web glue for .NET, written in C#..

K Scott notes Mark's awesome gravitar choice Jerry Statler

Mark closes by mentioning his participation in DDD (DeveloperDeveloperDeveloper!), Skills Matter Cloud Evening, and then Cambridge NxtGenUG (Next Generation User Group).

Show Links:

Mark Rendle, @MarkRendle

Dot Net Solutions London

Simple Data

Microsoft.Data

Rob Conery

NuGet

NHibernate

Entity Framework

SubSonic

DataMapper

autofac

StructureMap

Jon Skeet, @jonskeet

Scott Hanselman, @shanselman

Reactive Extensions

Open Wrap

Sinatra

OpenRasta

FubuMVC

Nancy

WebMatrix

Aaron Stannard, @AaronOnTheWeb

Jeff Schumacher, @CodeReflection

Jackson Harper, @jacksonh

OWIN

.NET Abstractions

Crack is now Fix

Fix ReadMe

Raven DB

Frack

Glenn Block, @gblock

Azure

Ryan Dahl

Seb Lambla, @serialseb

Jerry Statler and Conrad Waldorf

*Show notes compiled by* Ben Griswold. Thanks!

**Download / Listen:**

Herding Code 106: Mark Rendle on Simple.Data

**Herding Code 105: Brad Wilson on MVC 3** Feb 14, 2011
Show notes

**Episode 105**

In this episode of Herding Code, the guys talk to ASP.NET team member and repeat guest Brad Wilson about what's new in ASP.NET MVC 3, BDD-style testing with SpecFlow and WaitN, and the latest release of xUnit.net.

Jon begins the show by sharing Brad's bio and then dives right in asking about ASP.NET MVC 3 Service Location. Brad talks about DI and IoC, introduces the new feature and the implementation through such things as IDependencyResolver and Controller Activator. For the full story, you should check out Brad's eleven part series on ASP.NET MVC 3 Service Location.

Scott K asks why the MVC team didn't use MEF for dependency injection. Brad comments and brings up the prospect of using NuGet to install MEF support.

Scott K asks if MVC could ship as a NuGet package. The conversation shifts to how NuGet could allow MVC to further decouple it's shipping schedule from that of Visual Studio and the .NET Framework.

Everyone (Well, almost everyone. Kevin's being surprisingly quiet.) talks about jQuery plugins in the NuGet feed and how maintaining obsolete packages could get out of hand.

Jon asks about how the jQuery based unobtrusive validation system works in MVC 3 and asks if the ASP.NET Web Forms validation system could possibly take advantage of the new unobtrusive validation support.

Brad talks about the ASP.NET MVC development team and his role in developing ASP.NET MVC 3.

Jon runs through the big features which were shipped with MVC 3 - Razor, Service Location, NuGet, Unobtrusive Validation. Scott K mentions default templates are now using HTML5 doc types and Brad notes other MVC 3 features like Unobtrusive Ajax, Remote Validator, Json Model and Binding support.

Brad talks about extensibility for view engines in project templates and the new add view dialogue features.

Via Twitter, @gsogol asks if we will ever see fluent type configurations of filters, validations for controllers and classes.

Jon brings up the MVC 3 Futures library and asks Brad if it includes features which he wishes were rolled into the core MVC 3 bits. Brad explains the performance benefits of using the caching version of the model metadata provider system in the Futures library.

K Scott asks about feature requests for Display and Editor Templates and the guys talk about code based templates.

Jon talks about his favorable experience with Razor and mentions there's a web form to razor converter available.

@gsogol asks if the ASP.NET MVC team looks at other MVC frameworks to "borrow" various ideas for a more productive experience.

The guys talk about Razor Web Helpers like Web.Grid, Web.Crypto and Web.Mail which are baked into System.Web compared to the Microsoft Web Helpers which include social media helpers for Twitter and Facebook and video embedding.

The guys talk about the bundle of awesomeness which MS released with WebMatrix, SQL Compact and IIS Express.

The guys discuss what MVC3 offers to make testing easier and how one might unit test their JavaScript.

Brad talks about his love for BDD-style testing with SpecFlow, he explains the Given-When-Then syntax and how TDD and high-level spec testing complement each other. Brad mentions he would likely make the Web Steps he shared at Agile Conference 2010 available online soon.

Brad talks about MVC3 support in xUnit 1.7 and explains how xUnit compares to other test frameworks.

The conversation shifts to Swedish death metal and the guys totally nerding out about diet and fitness.

Brad pimps his Advanced ASP.NET MVC 3 talk at MvcConf 2 (video now on demand), teases us about his What's New in MVC 3 talk given at the P&P submit and mentions his January talk for the .NET Developers Association about, you guessed it, ASP.NET MVC 3.

Show Links:

Brad Wilson, @BradWilson

Scott Densmore, @scottdensmore

HERDING CODE 66: BRAD WILSON AND SCOTT DENSMORE ON IPHONE DEVELOPMENT

Patterns & Practices

xUnit.net

ObjectBuilder DI Framework

Brad's Service Location Blog Posts

MEF (Managed Extensibility Framework)

Ninject

Unity

NuGet

Visual Studio Gallery

Brad's Unobtrusive Client Validation Post

Brad's Unobtrusive Ajax Post

Html5

YUI

WebMatrix

Web Camps

Razor

Jeff Sogolov, @Gsogol

Razor-Converter Tool, Tsvetomir Tsonev, Telerik

Phil Haack

jqGrid, MvcContrib Grid

Wait, What's Node.js Good for Again?, ReadWriteWeb

Mary-Jo Foley

Orchard

PortableApps

Html Agility Pack

QUnit

Jurassic - a JavaScript Compiler for .NET - was mentioned by Jon and then Scott K mentioned Node.js (shocker) and referenced two other JS frameworks. Though the framework names slipped Scott's mind, he did mention Thomas Fuchs of script.aculo.us so we'll offer up those two links now and there may be more to come.

SpecFlow

WatiN

Agile Alliance

Nunit, Jim Newkirk

Cucumber

Arrange-Act-Assert (or "3A") pattern, William Wake

StoryQ

mbUnit

MachineSpecifications (MSpec), Aaron Jenson, @aaronjenson

SubSpec

The Primal Blueprint

Good Calories, Bad Calories

Scott Hanselman, @shanselman

Brian Henderson, @Brian_Henderson

Brad's Advanced ASP.NET MVC 3 Talk at MvcConf 2

.NET Developers Assocation

*Show notes compiled by* Ben Griswold. Thanks!

**Download / Listen:**

Herding Code 105: Brad Wilson on MVC 3

**Herding Code 104: Rob Eisenberg on Caliburn Micro** Feb 07, 2011
Show notes

**Episode 104**

You remember Rob Eisenberg from Herding Code Show #57 when he talked presentation patterns along with Jeremy Miller, Ward Bell and Glenn Block. Well, in this episode of Herding Code, the conversation continues as Rob talks with the guys about Caliburn.Micro, an opinionated MVVM framework for WPF, Silverlight and WP7.

Kevin kicks off this week's show asking Rob to tell us about Caliburn.Micro - his opinionated MVVM framework for WPF, Silverlight and WP7. Rob talks about how actions, support for conventions, and presentation roles are implemented in his opinionated MVVM framework.

Rob explains how about Caliburn - his earlier framework built for WPF - has contributed its most important features to the easier-to-use, lighter Caliburn Micro.

Jon brings up extensibility and inquires about how one overrides functionality in Cabiburn Micro.

Kevin and Rob talk about view resolution and the difference between ViewModel-First and View-First development which are both offered in Caliburn Micro.

Kevin asks designer integration and the "blendability" of Caliburn Micro.

Rob explains the convention-based approach Caliburn Micro takes toward bindings and actions and the guys speak to the importance of diagnostic mechanisms when your coding is based on magic of convention.

Kevin asks if that were places where the WPF/Silverlight/WP7 frameworks limited what Caliburn Micro could implement due to lack of extensibility points.

Rob dives into IResult and Coroutines and how one can write asynchronous calls in a synchronous a manner with Caliburn Micro. Rob then answers how coroutines compare to the implementation coming in C# 5?

Kevin asks about window management screen conductor and roles.

The guys discuss their experience working with Silverlight and WPF.

Jon asks about community contributions to Caliburn Micro and brings up the social aspect of open source and Mercurial projects in particular.

The show gets its first question from the hotline from Rick who asks, "What does Caliburn do that MVVM Light Toolkit does not do?"

Rob touches upon the Pub/Sub and window management features offered in Caliburn Micro and also talks about IoC friendliness.

The guys talk about Rob's elegant yet unorthodox approach to the service location in Caliburn Micro.

Rob offers a quick preview of what's to come next in Caliburn Micro.

Rob notes that he's submitted a talk for Mix11: "Build Your Own MVVM Framework with Html and JavaScript"

The guys discuss Knockout JS and its influence on Caliburn Micro.

The show wraps with Kevin (in Scott K's absence) asking THE question: "Is Silverlight dead?" Tune in and find out the answer to that one...

Show Links:

Rob Eisenberg, @EisenbergEffect

Caliburn Micro

Caliburn

Blue Spire

MonoRail

Jeremy Miller, @jeremydmiller

Herding Code 57: Presentation Patterns With Jeremy Miller, Ward Bell, Rob Eisenberg And Glenn Block

Build your own MVVM framework - MIX10

Build Your Own MVVM Framework...with HTML and Javascript - Mix11

Caliburn.Micro Soup to Nuts Pt. 5 - IResult and Coroutines

Caliburn.Micro Soup to Nuts Part 6a - Screens, Conductors and Composition

Matt Hamilton @mabster

Marco Amendola, @marcoamendola

Rick Ratayczak @RickRat

MVVM Light Toolkit

Ninject

MEF

Knockout, Steve Sanderson

MIX11

*Show notes compiled by* Ben Griswold. Thanks!

**Download / Listen:**

Herding Code 104: Rob Eisenberg on Caliburn Micro

**Herding Code 103: Seb Lambla on OpenEverything** Jan 25, 2011
Show notes

**Episode 103**

In this episode of Herding Code, the guys talk with "self-congratulatory, self-proclaimed, egotistical doofus" Sebastien Lambla about OpenRasta, OpenWrap and Open Web Interface for .NET (OWIN.)

K Scott kicks off the show asking Seb about his most popular OSS project - OpenRasta provides the 30 second elevator pitch and touches on his web framework which embraces HTTP through composition-based programming and facilitates the development of both JSON/XML services and webpage using the same fluent APIs.

K Scott asks Seb about OpenRasta Resources, Handlers and Codecs (oh my)and Seb outlines the four (yes, 4) main components of MVC, content negotiation and browser fun.

Scott K and Seb talk about the OpenRasta plug-in model and dig into pipeline contributors, operation interceptors and the full-flexibility of the OpenRasta composition framework.

Jon speaks of service location which are new to MVC3.

Jon asks Seb for his opinion on WCF Web APIs and how they compare to OpenRasta.

The guys talk about the distinction between the Microsoft Web and WCF frameworks and consider the creation of web services through .ASMX vs WCF.

Seb explains Easy, Simple and Intuitive in the context of existing frameworks and APIs.

Kevin asks about resource-oriented thinking in the .NET community. Seb response with talk of the slow adoption of RESTful architecture and poor education offered by vendors.

K Scott asks Seb when/why he started becoming passionate about REST and Seb shares his and OpenRasta's story.

Through the magic of Twitter, John Sheehan asks if there are any plans to develop a OpenRasta Client. Don't worry - RestSharp is safe for now.

Kevin asks a second question! Does OpenRasta do anything with hypermedia? Seb speaks of generating links and advanced links and forms (i.e. Hypermedia Controls) in OpenRasta.

Before the conversation shifts to OpenWrap, Jon asks about Seb's thoughts on OData and it not really being RESTful. Seb offers his option and notes his NDC presentation which brings light to all that is wrong with OData.

The conversation shifts to OpenWrap, a package management system for .NET. Seb provides a quick overview of the project and what it offers.

The guys discuss the release of NuGet and the collaboration (or not) with the Nu and OpenWrap folks during development.

The guys further talk about the various package management systems and the pros and cons around having more than one solution (with slightly different focuses) in the .NET space. Jon compares the situation to that of Entity Framework and NHibernate both coming to market. Seb talks about productivity.

Seb talks about dogfooding and building and deploying a package manager with the package manager.

Seb walks the guys through the typical workflow experience when using OpenWrap.

Seb explains what a symbol servers (specifically SymbolSource.org) offer and how it is to be integration with OpenWrap.

Seb provides an overview of OWIN (Open Web Interface for .NET) which defines a standard interface between .NET web servers and web applications.

The show wraps with Seb pimping his upcoming talks on OpenWrap and OpenRasta at QCon London.

Show Links:

Seb Lambla, @serialseb

OpenRasta

OpenRasta Getting Started

A Better ActionResult - A blog post by Garry Shutler on OperationInterceptors.

OpenWrap

OWIN - Open Web Interface for .NET

.NET HTTP Abstractions Mailing List

QCon London

Jeremy Miller,@jeremydmiller, FubuMVC

Glenn Block, @gblock, WCF Web APIs

Don Box

Clemens Vasters

OData

Seb's NDC2010 Talk: Using REST to Design a Better OData

restfully

Ian Robinson

Kayak

Frack

Knack

Fix

Manos

NuGet

Nu

RestSharp, John Sheehan, @johnsheehan

SymbolSource.org, Marcin Mikolajczak

OpenId

*Show notes compiled by* Ben Griswold. Thanks!

**Download / Listen:**

Herding Code 103: Seb Lambla on OpenEverything

**Herding Code 102: Tim Caswell on Node.js** Jan 19, 2011
Show notes

**Episode 102**

In this episode of Herding Code, the guys talk with avid open source contributor Tim Caswell about Node.js for which he is a community leader. Listen in as the guys dig into node.js and what it has to offer.

Tim gives the node.js elevator pitch and begins to explain what node offers - like event loops, evented IO, callbacks, non-blocking requests, high concurrency, and real-time scalability.

K Scott shares that Tim's wheat blog engine which sits on to of a Git repository was implemented using node.js.

Tim notes the greatest use case for node is still web development and touches upon how it differs from other framework like ASP.NET and Rails.

Scott K explains that he thinks of node as an abstraction over network programming and shares his excitement around the hundreds of interesting frameworks and modules developed with/for node.

Jon prompts Tim to talk about the node knockout competition and the various contest submissions.

Kevin asks for further explanation of evented IO and Tim provides further detail using a dentist waiting room analogy.

Jon asks how one troubleshoots callbacks and loops and how one manages state with node. Tim explains event based programming and why node.js came about.

K Scott asks if server-side js interest has recently exploded due to HTML5, web sockets and leaving connections open to the server. Tim talks about long polling and thread counts as opposed to the the node approach.

Jon asks Tim to speak about his extensive community contributions - namely his sharing of 47 repositories including wheat, step library for flow control and hamel.js. Not to mention the howtonode blog.

Scott K and Tim talk about sharing javascript code between the server and client.

Jon asks about kiwi, npm and node package managers.

Scott K asks how the node.js and server-side javascript got so popular. Tim turns to the need for a real-time web solution, social media and community involvement and Ryan Dahl's appealing personality and unique design strategy.

K Scott asks about Tim's tutorial on learning javascript through object graphs. Tim explains the importance of understanding that javscript doesn't operate like Java and the guys talk about jQuery's impact in learning (or not learning) javascript.

K Scott talks about a time before kids when IBM released an OS in javascript. Or was it Sun's Lively Kernel? Either way, it was before kids. You know what they do to one's memory.

Kevin speaks of the early, hyper-experimental days of node and asks if the community is starting to settle down and standardize on a set of libraries.

K Scott asks for Tim's thoughts on ECMAScript.

Via Twitter, Jackson Harper asks about no.de, a submission by Joyent into the node knockout competition, and it's current status.

Jon calls out Couch and Mongo and the NoSQL movement and Tim to share the node data story.

Scott K and K Scott talk about running Node on Windows.

Scott K dreams of IronJS and porting node modules to the DLR.

Jon asks how you get started with node and Tim recommends the friendly IRC room, the friendly mailing list and suggests a newb move to San Francisco and attend the frequent meet ups.

K Scott asks about Tim's everyday development environment and tools.

Kevin asks about the Node.js sweet spot. Is it for basic web development or is it geared towards more complex, real-time scalability problems? Tim discusses the perks and challenges of Node.js in any development undertaking.

Scott K throws out the "E" word and asks about node's penetration of the enterprise.

The show wraps with general conversation about node, Harmony and Javascript and Tim kind of misses his opportunity to pimp.

Show Links:

Tim Caswell, @creationix

Tim @ GitHub

Node.js

howtonode blog

V8 Javascript Engine

jsconf.eu

wheat

Sencha Labs

Miguel de Icaza, @migueldeicaza

Node Modules

Node Knockout

Ryan Dahl, Node

Matt Podwysocki's Blog

Haml-js

CouchDB

Step Library

TJ Holowaychuk (visionmedia), jade, kiwi

Dav Glass, @davglass, Node.js + YUI 3 Talk One and Talk Two @ Yahoo!

Isaac Schlueter, npm

Chris Williams's Blog, @voodootikigod, JSConf 2010, JSConf EU 2010

Learning Javascript with Object Graphs

Douglas Crockford

Brendan Eich

CoffeeScript, Jeremy Ashkenas

Rhino

SpiderMonkey

HTML5

ECMAScript5/Harmony

Jackson Harper, @jacksonh

no.de, Joyent

Nodejitsu

MinGW

Ajax.org Cloud9

Node.js Windows Port

MacRuby

IRC (irc.freenode.net `#node.js`.), developers mailing list

Sun Lively Kernel

Bruce Eckel

Express

Sinatra

*Show notes compiled by* Ben Griswold. Thanks!

**Download / Listen:**

Herding Code 102: Tim Caswell on Node.js

Herding Code 100: One Hundredth Show Celebration with Queen Beatrix Jan 02, 2011

Show notes

Episode 100

One hundred shows! Her Majesty Queen Beatrix shows up and talks with the gang about the previous 99 shows. Jon summarizes the server logs and beatboxes, K Scott talks about his jetset life via a flaky internet connection, Kevin reveals that this isn't the podcast he thought he was signing up for, and Scott K explains why The Fat Boys follow him on Twitter.

Download / Listen:

Herding Code 100: One Hundredth Show Celebration with Queen Beatrix

[music loop during autotune bit courtesy of Incompetech]

**Herding Code 99: David Ebbo on NuGet** Dec 02, 2010
Show notes

**Episode 99**

In this episode of Herding Code, the guys talk to David Ebbo, an architect on the Microsoft Web Platform and Tools team, about NuGet, a new open source package management system for the .NET platform.

David describes the history of NuGet - how NuGet evolved from a web-based feature for use in ASP.NET Web Pages and the inspiration from a web-based database admin tool by David Fowler.

Jon asks about how NuGet is related to the ASP.NET Web Admin site which was included in ASP.NET 2.0.

David then tells about how, at Scott Guthrie's prompting, the idea involved and how NuGet joined up up with the Nu project.

K. Scott asks about how NuGet works in practice using the Package Management Console.

There's a brief discussion of the name, and David foreshadows the impending name change to NuGet.

K. Scott asks about which packages are currently available, and what's involved in contributing a new package.

Scott K. asks about creating aliases, and David talks about the ability to change things via PowerShell.

David describes some of the logic involved in dependency management.

There's a Twitter question from David Alpert about customizing the package installation folder.

K. Scott asks if this is usable in all Visual Studio projects, not just web projects.

Kevin asks about configuration transforms.

K. Scott asks about the overlap between all the different developer installer systems - Web PI, NuGet, and the Visual Studio Extension manager. David explains how the focus of NuGet is very focused on bringing libraries into one project.

Jon asks if they've seen people using NuGet in ways they hadn't anticipated, mentioning a post by Eric Hexter on integrating NuGet and Solution Factory. David talks about how a NuGet package can include PowerShell scripts, which means you can add commands to the Package Manager console, describing how the NUnit package adds commands which allow you to run tests from the console.

Scott K. asks about the use of NuGet for... you guessed it... Javascript.

Kevin asks if NuGet could be integrated with the new project wizard.

Jon asks if there's any possible integration with Visual Studio Snippets. David explains how packages are including source code with sample code, and how this fits the use of project level source code better.

Jon asks about Web Activator.

K. Scott asks about how you'd run a local package repository. David talks about how you can do this by just putting packages in a folder.

Jon asks about how a package gets officially submitted and added to the feed.

Kevin remarks about the way NuGet is working as an open source project which accepts submissions from both Microsoft employees and the community.

There's a Twitter question from Elijah Manor about managing Javascript dependencies.

Kevin is happy to see the unit test coverage in NuGet, and asks about the unit test coverage requirements for package submissions.

Jon asks if there's any integration of Mercurial beyond the server-side package submission.

K. Scott asks about the possibility of future integration between NuGet and OpenWrap.

Jon talks about how he sees a lot of opportunity for NuGet to introduce some great open source libraries to developers and development shops which might not previously have considered using them.

Kevin asks if this is another example of a Microsoft initiative squashing existing open source projects. David talks about how NuGet was created to fill a void where they didn't see any leading package management systems for the .NET platform.

K. Scott asks about David's T4MVC project. David talks about how it's been really interesting and exciting for him as his first open source project.

Jon asks about how T4MVC is run on project build, and David mentions the Chirpy project.

Jon asks about how David divides his time between NuGet, ASP.NET Web Pages, ASP.NET in general, and T4MVC.

David ends with a call for contributions to NuGet.

Show Links:

David Ebbo (blog, @davidebbo)

NuGet

David Fowler (blog, @davidfowl)

Light up your NuGets with startup code and WebActivator

Eric Hexter (blog, @ehexter)

Using Solution Factory + NuPack to create Opinionated Visual Studio Solutions

OuterCurve Foundation

OpenWrap

T4MVC

Chirpy

Elijah Manor (@elijahmanor)

David Alpert (@davidalpert)

**Download / Listen:**

Herding Code 99: David Ebbo on NuGet

Herding Code 97: Jackson Harper on Manos de Mono Nov 16, 2010

Show notes

Episode 97

In this episode of Herding Code, the guys talk with Jackson Harper about Manos de Mono, his lightweight web application framework that runs on Mono. The goal of Manos is to simplify the entire process of creating, managing and updating a web application from prototyping and design to deployment. Manos aims to be Simple, Testable, High Performance, Reusable and Flexible. Sounds kind of dreamy, right? Listen in this week and find out how C# and Mono can be a viable option for web application development.

The show kicks off with Harper offering an overview of the Manos Web Application Framework. He notes his preference in using frameworks like Django over ASP.NET, his appreciation for Mono and C# and how these factors lent themselves to the creation of Manos.
Kevin asks what's different and interesting about Manos compared to ASP.NET MVC. Jackson speaks the philosophy of application development and digs into simplifying developer workflow.
Kevin asks what Manos includes. Harper lists off the simple routing, template engine and a non-blocking web server. He also notes that Manos will support any ORM and configuration management is in the works.
The guys talk about the simple and flexible routing system and continue to conversation by digging into Manos's html-centric templating engine.
Jackson walks through the developer steps to get going with Manos and is quick to note that Manos is not geared to the Windows developer. There will be Mac and Windows support but it is being build with Linux in mind.
Kevin and Jackson get into the core bits - what's included from the .NET Framework and what's custom built? Harper calls out that he's not referencing System.Web and his custom HTTP server is built on Tornado.
Jon asks about session management, authentication and security. Jackson talks about how the wish to ease deployment drove much of the implementation and custom component decisions.
Jackson further explains his interest in creating his non-blocking web server and why it benefits such operations as long pulling. This prompts Jon to asks if Manos is an alternative to learning Node.js.
Jackson talks about stealing users and pie.
Jackson talks about his strict No XML policy and how that will work into Manos's configuration management faculties.
Kevin and Jackson explore model binding in ASP.NET MVC and Manos.
Jon summarize what Manos has to offer - lght-weight, more html-like view engine, the routing system is nice, non-threaded architecture and high-performance - and asks how Harper decides what gets into Manos? Jackson explains the framework is more driven by need rather than trying to implement merely what other frameworks offer.
K Scott asks about the challenges of working with a static language, C#, in this space. Jackson flips the question on its head and talks about the benefits.
K Scott and Jackson talk about open and close mustaches, type safety, anonymous types and Manos's templating code.
Kevin asks about inspiration and Jackson reflects on how Manos came to be - starting with a focus on development flow to his need for a cleaner view engines to ease of deployment and then his interest in a non-blocking web server.
Jon asks about applications running on Manos and the long pulling niche.
Jackson talks about how .NET sets itself apart from other languages when it comes to parallelism and multi-core computing. Jon and Jackson talk about how parallel extensions are used in Manos and how Manos could be used to manage tasks on the server with C#.
@zbowling asks about the C10K Problem and the ability to handle 10,000 connections at once.
Scott K and Jackson discuss how have your own HTTP stack makes development and deployment a lot easier.
The show wraps with talk of route definition management, Sinatra and Cooking for Geeks.