Episode 19. Tainted edition. This is even a day later than we promised which we're really sorry about. As always, a big thanks to Chu Yeow, for the edge Rails updates and thank you to our sponsor Code Spaces. Here's a direct link to Chu Yeow's latest edge rails post.

Code Spaces The Rails Envy Podcast is sponsored by Code Spaces. Code Spaces is an online development and collaboration platform featuring subversion hosting, issue tracking, forums, and much more. Even better, it's a Ruby on Rails application so it's right up your street.

Subscribe via iTunes - iTunes only link.
Download the podcast ~16 mins MP3.
Subscribe to feed via RSS by copying the link to your RSS Reader


In this episode:



Question out to everyone: Is there any interest in an enhanced version of the podcast? We've noticed that the Apple TV now has a phenomenal podcast browser. If anyone is listening that way, we could spice it up with some graphics for each story. Would anyone mind the format switch to aac or m4a instead of mp3? Please let us know in the comments.

AddThis Social Bookmark Button Sections: Podcast | Tags: podcast  | Meta: 9 comments | permalink


Comments

Leave a response

Rob FunkFebruary 22, 2008 @ 10:17 AM

Hey, not all who listen to podcasts are using Apple products! I like to listen to podcasts on my portable MP3 player and my car stereo, neither of which knows AAC or M4A. (I think my desktop Linux machines can play them though.)

That said, if you want to do an enhanced version go ahead; for those who would get the enhancements it would be nice. But please don’t stop the MP3 version. And thanks for the podcast!


Jason SeiferFebruary 22, 2008 @ 11:31 AM

@Rob, That’s a really good idea that won’t affect any of the current listeners – just offer two versions. I think we’ll go with that.


Michael RakowskiFebruary 22, 2008 @ 06:51 PM

Regarding the enhanced version of the podcast:

Well, I generally listen to your podcast on the way to school on my iPod, which I wouldn’t be able to do if it was “enhanced” (I wouldn’t be able to see the visuals, which would probably make the podcast confusing if it was designed with a screen in mind).

I am still interested in the idea of the enhanced podcast. I currently am subscribed to ‘Railscasts’, which I generally watch if I am trying to do a specific task from the episode. I’d probably watch the first few episodes, but I generally don’t like sitting at my computer to watch/listen to a podcast. The idea of having two podcasts suggested by Rob sounds good. I’m curious what a Rails Envy enhanced podcast will be like. Definitely make a few episodes.

I don’t mind the change to aac or m4a, as long as it works on my iPod.


Jason RudolphFebruary 23, 2008 @ 12:15 AM

+1 for an enhanced edition of the podcast.


Jason SeiferFebruary 23, 2008 @ 01:52 AM

@Michael, the enhanced version would just let us add in graphics to go along with each story. You wouldn’t miss anything from the normal podcast except maybe we’d spice things up and throw in a logo for what we’re talking about at the time. Or a Rails can’t scale graphic or something.


Mike McKayFebruary 23, 2008 @ 12:20 PM

The cost of extra bling on a podcast that most people will never see (and probably take away from the stupid witty dialogue that makes it so great)… $200 in wasted uber hacker effort . The cost of podcasts coming out on time… priceless.

;-)

Stick to your knitting dudes.


Alan HarperFebruary 24, 2008 @ 07:29 PM

If you had an enhanced version I would subscribe, but for a short podcast like yours it wouldn’t have much value. Bookmarks on longer podcasts I do value though


Marcos OliveiraFebruary 25, 2008 @ 12:27 PM

Yes, would be great to have an enhanced podcast. I’m waiting for it.


Justin WeissFebruary 26, 2008 @ 11:00 AM

Advanced podcasts would be cool, but my pocket would probably be the only thing to see the cool pictures.

I liked the section on components, there’s a great discussion going on in the comments about using Rails components vs. writing a simple view-controller architecture within Rails, like Typo does for its sidebars. I tried something a lot like Typo for a project I just did, and it worked out great – you avoid making multiple requests per page, you can inspect the parameters that your components need (to autogenerate views for configuration), you can validate those parameters, persist the configuration to the database, and easily cache the result of rendering a sidebar with its parameters.

I whipped up a quick blog post that goes through some of the basics at http://blog.uberweiss.net/articles/2008/02/12/sidebars-are-better-than-components.

Keep up the awesome podcasts, they make my Wednesday commute (or Thursday commute, or Friday commute, depending on how many kids you guys end up with) a lot more fun.


Comment