perhaps these comments weren't meant to be analysed or taken seriously, but if your position is that community-minded sites facilitating an exchange of information are not a real world use of the internet then that seems at odds with, well, the internet. ask yourself why you are compelled to keep visiting a website that appears to fall into your category of not being of the 'real world' to post your opinion to. then probably visit this link to compare your ideas with some others.
So, you are saying that RoR is only suitable for internet projects? I thought it was also being touted as the J2EE killer for web applications in general? If you constrain your set of applications enough (two guys working in a garage, creating socially impacting fluffy websites), I'm sure RoR becomes very significant. But don't try to
tell me with a straight face that it is the cure all for corporate webapp development.
fair enough. then sit on the fence rather than slinging mud
Sitting on the fence slinging mud is rather easy when the RoR crowd goes swaggering down the middle of the
street stark naked yelling about their new clothes. I saw the same parade go by a few years ago comprised
of Java fanatics. And, before that, VB fanboys ("oooh, look, I can make a button that pops up hello world!")
And, before that, C++ nuts. With minor throngs of Python groupies and PERL diehards along the way.
Which, as I mentioned elsewhere, is the response I always get.
What bright-eyed, dewy-fresh CompSci grads don't seem to get is that the real world
doesn't care about elegance and purity. Real world data stores care about things like
optimizing and caching stored procedures, compliance with SarbOx security issues, and data
safety.
No, I don't consider websites that help you organize your class reunion or camping trip
to be the real world.
i've NEVER experienced this. never never never. and i have no idea what you're talking about. one of the real clinchers of rails for me is its use of ActionRecord to interface with the database. i modify my database constantly without breaking any code. the only case i can think of when what you describe could happen is if i were to rename a column in the database, then my row.name object wouldn't match. but i would consider a broken website due to this the fault of a stupid developer.
But what if you are working with 4 developers and 4 DBAs? And all data is accessed through stored procedures?
Anytime I bring this up, I am usually met with "oh, well you know RoR isn't a perfect fit for *every* project."
So what is it a fit for? Folks push it as a J2EE killer but under pressure start saying it's more suitable for
things like "Name a Star for your Pet" website.
to be able to connect to my database, retrieve a record and update it, in 1 line in some cases, becomes rather neccessary for a developer once they've tried it.
Mydb.update(id,:name => 'John')
will do all of these. i take a wee dance on the grave of large-scale php development everytime i use that.
And any coder of any talent would have already created the routine as part of their toolbox for their language
of choice. It is one of the first things I write for any new language that I use in a datacentric project.
large scale use of rails is very easy to find if you visit the rails site . It's also very easy to find a larger list, and a list of interesting apps to boot. granted, not moving pictures, but.. oh go away.
When I see a company with > 50 million USD in revenue using it for mission critical apps, I'll sit up and pay attention. Until then, it seems best suited for "10 Things To Do Before I Die" type websites.
Also, RoR's ORM does not play nicely with stored procedures. Bring this up to any die-hard Rails fanatic and they will start spinning: "You don't need it! Stored procedures are satanic and force business logic into the data store."
Which makes me think that most RoR pushers don't have experience with large corporate DBs.
A nasty side effect of RoRs current popularity is that it completely overshadows some very good Ruby web frameworks such as IOWA and Amrita
Slashdot Mirror
Sitting on the fence slinging mud is rather easy when the RoR crowd goes swaggering down the middle of the street stark naked yelling about their new clothes. I saw the same parade go by a few years ago comprised of Java fanatics. And, before that, VB fanboys ("oooh, look, I can make a button that pops up hello world!")
And, before that, C++ nuts. With minor throngs of Python groupies and PERL diehards along the way.
Which, as I mentioned elsewhere, is the response I always get.
What bright-eyed, dewy-fresh CompSci grads don't seem to get is that the real world doesn't care about elegance and purity. Real world data stores care about things like optimizing and caching stored procedures, compliance with SarbOx security issues, and data safety.
No, I don't consider websites that help you organize your class reunion or camping trip to be the real world.
True, and my bad (realized what I had said as soon as I hit submit).
All the same, RoR fans give the impression that RoR is the *only* way to do web dev in Ruby while ignoring Nitro, IOWA, and Amrita.
So what is it a fit for? Folks push it as a J2EE killer but under pressure start saying it's more suitable for things like "Name a Star for your Pet" website.
And any coder of any talent would have already created the routine as part of their toolbox for their language of choice. It is one of the first things I write for any new language that I use in a datacentric project.
When I see a company with > 50 million USD in revenue using it for mission critical apps, I'll sit up and pay attention. Until then, it seems best suited for "10 Things To Do Before I Die" type websites.
You are very much correct.
Also, RoR's ORM does not play nicely with stored procedures. Bring this up to any die-hard Rails fanatic and they will start spinning: "You don't need it! Stored procedures are satanic and force business logic into the data store."
Which makes me think that most RoR pushers don't have experience with large corporate DBs.
A nasty side effect of RoRs current popularity is that it completely overshadows some very good Ruby web frameworks such as IOWA and Amrita