From: "M. Edward (Ed) Borasky" Date: 2006-07-28T14:35:44+09:00 Subject: Re: About last night ... James Britt wrote: > More important, it would indeed be a shame for people to miss the > annual RubyConf simply because of bad timing when hearing about start > of registration. Is that likely? Given that a large portion of > interest is in Ruby as Rails, and not Ruby itself, I wonder if the > recent Rails cons will have satisfied people who may now be less > motivated to attend the Ruby conference(s). Well ... the 16 presenters will be there, and the conference organizers ... that's probably at least half a dozen. I'm guessing all the folks who submitted proposals that were rejected want to go anyway, so there's almost 100 right there. > I know others have been discussing local conferences. One question > that has come up is what will draw the best crowd, and what crowd > should one be looking to attract. Specifically, turn out for a > regional Ruby conference vs. a regional Rails conference. When one > talks of Ruby resources and nuby demand, is the demand for Ruby > programming knowledge or Rails API support? (I know, this is a > simplification, but I think it focuses the main idea.) After reading David Black's "Ruby for Rails", I'm finding it exceedingly difficult to separate the two of them. Quite frankly, I don't think you can call yourself a Rails developer unless you're a *strong* Ruby programmer. Sure, you can put together a cookbook, maybe even a wiki or a blog, just knowing how to use a browser, a text editor and all of the built-in capabilities of Rails, without a deep knowledge of Ruby. But a *real* web app? No way! Amy said it last night -- "Rails is a gateway drug". With hotel costs and air fares being what they are these days, I think I'd *prefer* regional conferences. Some of the most amazing Ruby is coming out of the Seattle Ruby Brigade, for example. I don't know where many of the other folks on this list call home, so I don't know what other cities would be logical places for a regional conference. > I'd hate to find that I can't attend the Denver gathering because I > got to the Web site too late (though my army of tireless robots shall > be unleashed momentarily!!!) and I have to believe many others feel > the same way. And I'd hate to see the event become "exclusive" or > viewed as such (despite knowing that David, Chad, Rich, et al would > never intend such a thing). On the other hand, I like the idea of > smaller assemblies. There are notable differences in gatherings of > 12, 25, 55, 240, and 500, and I can appreciate David's interest in > capping registration. Well ... I can tell you point blank I won't write a bot to poll the site. If I don't get to go, I don't get to go. I'll survive, I'll go on coding and lobbying for a regional conference in the Pacific Northwest. I just wonder about a programming language whose creator and early adopters have become a smaller-scale equivalent of rock stars. I can't recall that *ever* happening before. In fact, I can't recall *any* piece of software where that's happened! The scary thing about this is that such high-powered demands are often a bubble, which eventually bursts in a spectacular way. That's not something I think anyone wants to happen to Ruby, or even to Rails. > > Perhaps, if avoiding the enterprisy-ness of multi-track, 500+ attendee > conferences is a useful goal, then there should not be just the One, > True RubyConf, but several regional ones, across the globe. Perhaps > that's more agilely. > > Or it may be non-issue if people have a choice between Rails and Ruby > conferences; RubyConf may go back to ~50 people who all know each other. I doubt that very seriously. I have to admit my motivation for going to the conference is more to meet the big names in Ruby than it is to see all sixteen of the chosen talks. There are at least ten that contain something I could use, but it's also about being with people who "speak the same language".