Moxley Stratton wrote: > Hello all, > > I'm new to the group. You may remember me at your Free Geek meetings. > I'm the PHP user group guy who sometimes holds your projector hostage. > Sorry about that. > > Anyway, I've been hired to work on a new project. It is a new > collaborative/social web site in the vein of Wikipedia and MySpace. I > really want to do the site in Ruby because I like it and I'm getting > tired of PHP and it's wimpy language design. > > PHP is my fall-back choice if I can't quickly strategize a Ruby > solution. It is a much larger phenomenon than Ruby, and it has a proven > track record on large sites, like Yahoo for instance. As far as I know, > Ruby doesn't have such a track record for web development. > > My first-choice Ruby strategy is to use mod_ruby and use a development > style that looks a lot like my PHP style, wherein I start from scratch > and develop a framework around the requirements instead of trying to > tweak an existing framework (e.g., Rails) to fit the requirements. Rails > seems too constraining for the complex data access and performance > requirements of this project. I'd like to hear opinions about this. > > Regardless of what Ruby strategy I take, it really would be great if > there was a solid software designer with real-world Ruby web experience > who could partner with me with design decisions and maybe code too. It > would be part-time help and it would start right away. The site is > expected to launch in about six months. > > Best regards, > > Moxley Stratton > http://www.moxleystrattton.com/ > > _______________________________________________ > PDXRuby mailing list > [email protected] > IRC: #pdx.rb on irc.freenode.net > http://lists.pdxruby.org/mailman/listinfo/pdxruby > > If you pick up Hal Fulton's second edition of "The Ruby Way", you'll see a couple of web frameworks. There's Rails, of course, which is the "800 pound gorilla". But there's also a good writeup on IOWA and Nitro, and one of these might be a better fit than Rails.
Nitro has a different approach to ORM than Rails does. Essentially you define your objects and the way they relate using the Og (Object graph) operators. Once that's done, the framework defines the database. I haven't had a chance to play with it, but it's definitely worth a look. P.S.: You'll probably want to look at PostgreSQL as the database rather than MySQL; MySQL is better than it used to be, but PostgreSQL is more of an "industrial strength" database. -- M. Edward (Ed) Borasky, FBG, AB, PTA, PGS, MS, MNLP, NST, ACMC(P) http://borasky-research.blogspot.com/ If God had meant for carrots to be eaten cooked, He would have given rabbits fire. _______________________________________________ PDXRuby mailing list [email protected] IRC: #pdx.rb on irc.freenode.net http://lists.pdxruby.org/mailman/listinfo/pdxruby
