I’ve not seen this posted anywhere else on the list…
You may have already heard about Ruby on Rails, the new application
framework that seems to be taking the Web development community, in
particular J2EE and PHP programmers, by storm.
Rails is a capable Web application platform and has, in less than two
gained significant traction among J2EE and PHP programmers. The
of both J2EE and PHP programmers makes a lot of sense when you look at
strengths of Rails. For one thing, it uses a strict
architecture that any self-respecting design-patterns wonk would
explains its attraction to J2EE developers. Second, it’s easy to build
systems with Railsâ??which is attractive to PHP developers.
However, Rails has some pretty significant limitations from a database
perspective. Rails makes a lot of assumptions about your database layout
application needs. For example, Rails assumes that all tables use a
non-compound, primary key. Compound primary keys are not supported! In
addition, Rails does not support two-phase commit; it’s designed to be
against a single database backend.
This article is not intended to be a booster piece for Rails nor is it
expose. It’s simply an introduction to the technology. It contains both
praise and criticism. At times the criticism might appear a bit heavy
(especially to Rails enthusiasts), but don’t be fooled. Using any Web
application framework is going to be tricky, whether it’s J2EE, ASP.NET,
PHP. In the long run, you can be a lot more productive with Rails than
can be with many other Web application development platforms, but it
time to learn the ropes."