| The Rails Progress Report: The Good, the Bad, and the Ugly. |
[Nov. 16th, 2005|02:41 pm] |
I'm having a ball so far with Rails on the new project. Here's a rundown on how things are going so far.
The Good:
* It's easy to get Rails app up and running fast
* Rails' Model, View and Controller tie together in an intuitive fashion
* The ability to make and see changes on the fly in Rails is awesome
* Rails is feature rich, including TDD features
* PostgreSQL has worked out well so far
* Guy Decoux put out an updated pl/ruby for PostgreSQL 8.1 and it seems to work well
The Bad
* The Rails book doesn't cover config/environment issues very well
* PostgreSQL has no "create or replace table"
* Generating default scaffolding is problematic when you don't want to use the default table naming scheme
* Views in Rails seems to get confused by foreign keys referencing columns in tables with identical names.
* The traffic on the Rails mailing list and #rubyonrails is too heavy for my liking
The Ugly
* Attempting to do ldap searches via ruby-ldap causes WEBrick to core dump in 1.8.2 (but apparently fixed in 1.8.4p1).
Of the issues I listed in "The Bad", none are too serious. The traffic issue is unavoidable. In the case of the foreign keys issue, I just prepended all column names with "table_", except for the id. Only the WEBrick core dump caused by ruby-ldap is a major concern, but Ruby 1.8.4 will be out soon. Of course, there's still the "make" issue to work out for Solaris, but I'm hopeful. |
|
|
![[info]](http://l-stat.livejournal.com/img/userinfo.gif){kind=small}
djberg96's journal