Yehuda Katz talks about the merge of Rails and Merb to what will become Rails 3.

The first topic is ORM agnosticism and ActionORM, an abstraction to other ORM interfaces to make it easier to use alternatives to ActiveRecord (3:00).

Merb still evolves (11:10) and accumulates new features (Controller#call, Router#call) from Rails 2.3 that will also be in Rails 3, to make Rails and Merb similar enough to allow an easy migration.

At 17:50, Yehuda elaborates on some of the refactoring that is currently going on: cleaning (and also speeding) up of Callbacks, a bottleneck found through profiling; removing of old and confusing code in ActionPack (21:52) and separating code into new frameworks, like ActionDispatch (24:00)

Merb 1 has three different kinds of APIs (public, private and plug-in, 28:25), Rails will also get a plug-in API, but the specifics are yet to be decided.

Rack::Bug (30:55), inspired by the DJango Debug Toolbar, will make debugging and the writing of instrumentation code easier.

Last but not least (33:53), they want to make sure that JRuby and Ruby 1.9 can run Rails 3.

Kirk Haines from Engine Yard explains how Vertebra, their framework for managing fault tolerant services, is comprised. He starts with the foundations: the XMPP based protocol (2:54) and the Ejabberd server (5:15).

Agents (5:55) run on your machines in the cloud and provide a certain service, which they register at a Herault (7:30). Those services can then be discovered from client agents from the Heraults (9:30). Herault's also handle authorization (10:06).

If you have several agents providing the same service, you can use a Scope (11:56) to control how the operations are distributed.

After this introduction, Haines elaborates on the libraries and frameworks they used to build Vertebra as well as the problems they encountered: XMPP4EM (14:05), Loudmouth (14:28), EventMachine::Deferrable (15:23).