disadvantages of Ruby on Rails

It is so nice to use that it makes your day job seem an even more
depressing.waste of time than it did before.

Seriously though Rails does have its weak spots. In no particular
order I see them as

- Creating 'Forms and Reports' applications seems much more long
winded than it should do. The 'view' part of Rails simply hasn't got
any meat on the bones. Despite RJS, etc you still find yourself
messing around in HTML and CSS at a very low level.

- Using resources, as opposed to providing them, seems a lot more
difficult than it should be. I feel that the interactive part of an
application should simply be consuming REST resources provided by
other facilities (on the same box or elsewhere), but it is just seems
very difficult to do that in Rails at the moment.

- Infrastructure support for Rails is still poor. There is no qucik
way of setting something up that handles backups and restarts
efficienctly and manages traffic into your site so that it doesn't get
Slashdotted.

- Some Rails techniques out there are bad for your application's
health. For example overuse of storage in the session, and lumping all
users in the same database. This all comes from the Rails Tutorials
which have become 'best practice' despite the fact that they were
never intended to be so.

- The documentation and ideas about Rails are scattered around the
Internet on blog sites, with very little consolidation. Blogs may be
easy to use, but they are the worst sort of knowledge store. The
central wiki is an appalling mess that desperately needs a good clear
out.

But despite all that, it is worth sticking with because Rails is so
damn nice to use.

(And if anybody has suggestions has to how to alleviate the pain of
the above, please let me know).

NeilW

MasterView is a gem/plugin for Ruby on Rails which allows you to create views that you can WYSIWYG edit them and not have to fiddle directly with HTML and CSS as much. Use tools like the open source NVU or Dreamweaver to do the editing (even give this to a designer to work on). And these new views, retain all the nice features of rails including layouts, partials, and use of helpers. You can start from an html prototype and make it real or use the built in generator to get you a CRUD set of views set up.

We have a demo of the second usage up on the website here

http://masterview.org/videos/demo_short.html

Main site:
http://masterview.org/

Rubyforge project: http://rubyforge.org/projects/masterview

If you have any questions about the project or its focus, send them my way.

Jeff

Hi,
    I am a developer on Ruby on Rails from 6 months...
    We developed Rails application using the Apache(Configured with
mongrel) server,the problem is we are developing a integrated generic
application where the application is one,clients are many so on the same
server many users can access the application.We are facing the
performance issue.When multiple users accessing the application it is
working very dead slow since it having large database and lot of
different functionalities ...
    Is there any way to increase the performance?

Jeff Barczewski wrote:

Could you give us some numbers, like the actual hardware you're using
and the number of clients?

Right off I can think of a couple of things, like obviously making
sure you're running Mongrel in Production mode and making use of
Caching. There are a ton of different Rails performance tools
available including FiveRuns TuneUp and NewRelic.

With some real numbers, we can probably throw out some real ideas.

Alex Conner wrote:

Could you give us some numbers, like the actual hardware you're using
and the number of clients?

Right off I can think of a couple of things, like obviously making
sure you're running Mongrel in Production mode and making use of
Caching. There are a ton of different Rails performance tools
available including FiveRuns TuneUp and NewRelic.

With some real numbers, we can probably throw out some real ideas.

On Jan 23, 1:02�am, Hema Gonaboina <rails-mailing-l...@andreas-s.net>

Don't forget to add the correct indexes to your Database. Please give us
some figures such as number of requests per day and per second, time to
process a request, type of hardware, etc.

Jeff Barczewski wrote:

MasterView is a gem/plugin for Ruby on Rails which allows you to create
views that you can WYSIWYG edit them and not have to fiddle directly
with
HTML and CSS as much. Use tools like the open source NVU or Dreamweaver
to
do the editing (even give this to a designer to work on).

Ruby In Steel has a full page, drag-and-drop WYSIWYG visual design
environment for Rails. You can either design the pages inside Ruby In
Steel or you can share them with a dedicated designer such as
Dreamweaver.

More info here:

http://www.sapphiresteel.com/Visual-Rails-Workbench-The-Import
http://www.sapphiresteel.com/A-Brief-Guide-To-The-Visual-Rails
http://www.sapphiresteel.com/A-Brief-Guide-To-The-Visual-Rails,235

Short screencast here:

http://www.sapphiresteel.com/Visual-Rails-Workbench-screencast

best wishes
Huw

SapphireSteel Software
http://www.sapphiresteel.com