Well, lets be empirical. Here's a real Rails site: http://communitywalk.com
communitywalk.com is a RoR site that was developed at my current employer, usually by one or two pairs at a time, with most of the work done by the site owner (who is an employee too). I didn't work on it much (was mostly done when I came on), but I'd say they probably spent about 2-3 pair months of the total dev time optimizing performance. Maybe a lot less. It's a cool site, and it performs pretty well. I guess you'd call it Web 2.0, there's Google maps and lots of Javascript, but I wouldn't call it sleazy :) We're currently running it (MySql DB and Lighty/Rails) on a single Xen virtual machine on a new Xeon box. I think it's about in the 30-40 Gig/month bandwidth range - not sure on hits. Not huge traffic, but not tiny, considering it's all on one box. How would you quantify an impressive load for a site to handle and still have good performance? -- Chad On 6/24/06, josh zeidner <[EMAIL PROTECTED]> wrote:
Hi Erik, After having worked with countless web frameworks and dozens of languages I will say this: What you gain in development effort and 'syntactic sugar' you lose in performance. As all these sites prop up I just give it a year or two before people start marketing themselves as experts in 'optimizing' RoR, so they can sell the solutions to the performance problems that the 'peace and contentment' caused. Very similar with EJB and CMP. EJB offered a simplistic layer of abstaction that made data management simpler, but also caused a huge expense in the management of the EJB container! Secondly, if Ruby can offer more to the client, then the RoR programmer will charge more! Aren't labor economics fun? EJB in the end, didnt save anyone a cent. There is nothing new under the sun, but there is a never ending supply of idiots and people willing to pay them. Having witnessed the Web 2.0 sleaziness first hand, I do not trust anything that is associated with that world. If you want to deliver something really good to your client, give them standards that are unencumbered by licenscing constraints( where it is affordable of course ). I still do respect Java as a language because the semantics are well established. The changes that it introduced to C++ syntax were well accounted for. sincerely, jmz --- Erik Hatcher <[EMAIL PROTECTED]> wrote: > > On Jun 21, 2006, at 9:08 PM, josh zeidner wrote: > > RoR: Why? because its Web 2.0( see CMP Media > > scandal ). The whole Web 2.0 thing( which RoR is > > invariably linked to ) has turned out to be a > very > > stupid multi-level marketing scheme starring Tim > > O'Reilly. RoR offers no technological advantages > over > > existing scripting languages, despite the magical > > claims of its proponents. > > My good (virtual) friend, Brent Ashley told me > recently "if Jesse > James Garret is the father of AJAX, then you and I > are the mailmen > that all the kids look like". Back in the Tucson > days, between > getting .bombed by Running Start and starting at > eBlox I wrote an > article about Remote Scripting for developerWorks > which was my first > foray into technical writing. > > No technological advantage? I disagree. The > brevity and > readability... let's just say "succintness" most > definitely is > advantageous. For example, to wire up a > Google-Suggest-like drop- > down box I put this in my template: > > <%= text_field_with_auto_complete :agent, :name, > :size => 20 %> > > And there is a controller method that generates the > <ul> that gets > rendered. There is a lot of convention, over > configuration, and > sometimes that is a bit too "magical" even for my > tastes. > > But I can confidently say that RoR will be my > preferred front-end > technology for the foreseeable future and with > loosely coupled back- > end technologies, such as Solr, it's trivial to tie > the best of breed > pieces together, Java (or otherwise). > > Erik >
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]