Hi, I agree with the point that Giles makes in response to the comments by Jason. Also, I would like to say that market share doesn't mean anything. For example, more people are using PHP than Rails. Also, more people are using Java than Rails. Please don't get me wrong but I do like Rails as well as its community but don't try to pit Seaside against Rails. It's a different framework for building web applications. One of the prerequisites of Seaside development is to be fairly comfortable with Smalltalk. Also, one needs to be comfortable with Ruby to be proficient at Rails. Next, agile developer should be a part of the solution instead a part of the problem. Thus, in the open-source community, if something doesn't exist, you build it and/or assist in its implementation. For example, Alan Knight has built GLORP and is also working on an ActiveRecord implementation. Seaside is a community effort and it should be treated as such. Jason, what are you doing to provide support to Seaside instead of pointing out its shortcomings in comparison to Rails? I'm sure that there's a list of enhancements that need developers to implement.
<div><br class="webkit-block-placeholder"></div><div>-Conrad<br><div><br> </div><div><div><span class="gmail_quote">On 7/17/07, <b class="gmail_sendername">Giles Bowkett</b> <<a href="mailto:gilesb@gmail.com">gilesb@gmail.com
</a>> wrote:</span><blockquote class="gmail_quote" style="margin:0;margin-left:0.8ex;border-left:1px #ccc solid;padding-left:1ex">> The bulk of my development work has been in Java, Smalltalk and Ruby<br>> (~60%, ~10%, ~30% respectively). I have done quite a bit of
<br>> development in Rails. With this background, I would like to offer one<br>> more reason why I think Rails gets more market-share than our beloved<br>> Seaside.<br>><br>> Hypothesis: many developers get sucked into Rails and the RailsWay
<br>> simply because it's so easy to prototype new apps or get quick and<br>> dirty solutions running.<br><br>I think this is true. I'm pretty sure ease of adoption is a priority<br>for Rails core. But I don't think this is necessarily such a problem.
<br>Rails apps, because of the incredibly gentle learning curve, are kind<br>of a magnet for bad code. The goal isn't to take over the world or<br>whatever. Just because lots of people are into Rails doesn't<br>necessarily mean your Rails experience will be a good one.
<br><br>--<br>Giles Bowkett<br><br>Blog: <a href="http://gilesbowkett.blogspot">http://gilesbowkett.blogspot</a>.com<br>Portfolio: <a href="http://www.gilesgoatboy.org">http://www.gilesgoatboy.org</a><br>______________________________
_________________<br>Seaside mailing list<br><a href="mailto:Seaside@lists.squeakfoundation">Seaside@lists.squeakfoundation</a>.org<br><a href="http://lists.squeakfoundation">http://lists.squeakfoundation</a>.org/cgi-bin/mailman/listinfo
/seaside<br></blockquote></div><br></div></div>