Rails Envy

Hi -

On slide 50 (actions/sql/rest table) I believe the SQL for ‘create’ should be ‘insert’ ?

Not a big deal really, but thought I’d mention it.

Nice presentation. One comment I had (as an unRESTful skeptic) was that the argument for REST would be strengthened by tackling more complex “problem” areas for RESTful architectures. An example might be a dashboard-type view. Where would such an amalgam fit, both in Rails 2.0, and in the overall REST-based worldview? Is it an edge case? Is there a new way to think about/build such a page? (I know that this was an RPC-focused talk, and so wouldn’t necessarily fit this particular presentation, but am interested in your thoughts)

Regardless, am slowly being won over to REST as a positive step in webapp best-practices evolution, in no small part due to evangelists such as yourself. Cheers!

This was great. Your presentations are pretty cool. It’s always way more informative to have someone tell you why something is useful and exemplify it’s usefulness, as opposed to just telling you what it is in technical terms. I had already adopted the REST paradigm a few weeks ago but this presentation definitely enhanced my understanding of it.

Great presentation, but I also want to second Rob’s comment.

I am a huge rails advocate and am very curious about these RESTful techniques, but so many of the examples I see are so incredibly simple and narrow they don’t seem to handle more intricate and complex examples. I’ve built several very large and complex social networking type sites in Rails and really can’t see how some of the complexities I’ve had to deal with would fit into this without some major shoe-horning of a round peg into a square hole. I’m more than open to be proven wrong, but I’ve yet to see anyone address something of real complexity.

I also found this to be the case with many Rails tutorials as well. I understand that doing demonstrations and tutorials need to be centered around very narrow cases to be understandable, but when talking about something as all encompassing as application design from top to bottom, it would be great to see something with more depth and complexity than posts and comments with 2 fields each.

I do want to reiterate that I’m not complaining about the current content. I love the stuff you guys do and anxiously await the next thing. I’d just like to throw a vote in for something more involved down the line.

Well my view is that both REST as well as WS-* have their own uses and Rails would benefit being able to use them both based on the solution context. If there are concerns handling complexity with REST, the ideal is to consider a mix with SOAP and REST.

Can someone post a non-Quicktime version of the talk? It looks really interesting and I love the dual PPT Presentation view - but the audio is all fubared on the two Windows Vista machines I’ve tried it on. Maybe I’m just the last Rails user to use Windows.

Also, dudes - you guys rock. I would love to see some more hard technical content coming out of you guys. I always listen to your podcast hoping for the day when you do more than a headline read. I’m not saying it’s a bad thing, I just wanted to chime in and let you know that there’s someone out there hoping to hear some more in depth discussion from you guys!

I like Thomas, the last Netbeans user on the planet. I’d like to hear how many 5-year-olds he can handle.

If you get “env: ruby: No such file or directory” then check here:

Great presentation. Just found your podcast today and am quickly catching up 8-). How did you do the video with the split screen? That really helped being able to watch the slides and you talk at the same time. Just curious.

Keep up the great work!