What is OmniNerd?

Welcome! OmniNerd's content is generated by you, the reader. Through voting and moderation we strive to highlight the nerdiest of what's around and provide content that's a little more thought provoking than other sites.

Submit New Content

Voting Booth

Ever lie?

View Results, All Polls
16 votes, 1 comment
1
Nerd-It
+ -

Rails Locks The Framework

Comment comment by VnutZ on 14 January 2008

I have to agree that Ruby on Rails definitely makes things a lot easier. Now, I'll be the first to admit I contributed next to nothing (other than the bug system) in terms of code used to run OmniNerd. However, from that experience, it is very easy to go from idea to concept to production when using the Rails motif.

I think one of the big hesitations on converting has to do with how big a shift it can be for an existing webpage. Say you were a PHP programmer and had to change some material into a new language, fundamentally, it's an exercise of converting syntax. Most of your actual logic and layout really does remain the same. Ruby on Rails requires an overhaul of structure to fit into the framework. And that locks you in unless you find an alternative Language on Rails. I think that committal step is what keeps Rails from getting as adapted as it could be. Existing sites don't want to change and newcoming sites question what happens if Rails goes away.

You are a viewing a subset of a larger discussion.
View Full Discussion
Star This to Save in Your Profile Favorite
Thread parent sort order:
Highest Voted : Lowest Voted : Oldest : Newest
Thread verbosity:
Expand All : Minimize Replies to Comments
0 Nerd-Its - +
RE: Rails Locks The Framework by scottb :: NR7

Ruby on Rails requires an overhaul of structure to fit into the framework.

That's not strictly true. It's fairly easy to ignore the Rails controller/view separation if you want. If your old code is written in a fully embedded scripting/templating language, like JSP or ASP, then you can get a similar effect by putting all of the logic in the Rails view.

If the old code is written in a code-only style, like a CGI script or a Java servlet, then you can put the whole thing in the Rails controller.

Neither of those is recommended, but they'll get you switched over to running under Rails rapidly, so you can take your time in refactoring it into a "proper" MVC style.

Posted 14 January 2008, Hide, Parent, Reply