February 19th, 2005

Of high-level components

Heh, something that I wanted to write about:

One of the clear goals for Rails from the start was to stay at the infrastructure layer. I didn't want Rails to succumb to the lure of high-level components like login systems, forums, content management, and the likes.

Thank God!

Warren told me about the introduction of something—I don’t remember at the moment—some high-level component; that got me worried.

Rails does use certain components—“link_to”, “text_field” (as Jamis commented)—and this is perfectly acceptable. When you have a high-level component, you tend to reuse that component—even if ultimately it may not serve your intended purpose all that well. Yes, “all that well” is very subjective. There probably is a tradeoff between the duration of the project and acceptability of using high-level components. And I’m afraid I don’t think the relation is very straight forward. If there’s data relating to this that you’re aware of, please let me know.

I could come up with some figures, but it’s going to take me some time.

Posted at 04:04 pm | Link | 8 comments | Leave a comment