On Mar 6, 11:03 pm, Jason Hsu <jhsu802...@gmail.com> wrote: > I'm currently in the process of learning Ruby on Rails. I'm going through > the Rails for Zombies tutorial, and I'm seeing the power of Rails. > > I still need to get a Ruby on Rails site up and running for the world to see. > (My first serious RoR site will profile mutual funds from a value investor's > point of view.) > > I have an existing web site and project called Doppler Value Investing > (dopplervalueinvesting.com) that uses Drupal to display the web pages and > Python web-scraping scripts to create *.csv and *.html files showing > information on individual stocks. My site has a tacked-on feel to it, and I > definitely want to change the setup. > > At a future time, I will rebuild my Doppler Value Investing web site in > either Ruby on Rails or Django. The Ruby on Rails route will require > rewriting my Python script in Ruby. The Django route will require learning > Django. (I'm not sure which one will be easier.)
It is a natural programmer instinct that a uni-language solution is felt cleaner than a multi-language one. This feeling is valid under the following assumptions: - You are starting from ground up - The investment in learning something new is not considered significant In your case, with a site already up (maybe with a tacked on feel) and learning django a significant effort compared to directly coding in RoR, you should look at polyglot solutions more carefully (eg not directly relevant ... something like http://www.igvita.com/2009/03/20/ruby-polyglot-talking-with-erlang/ ) IOW code your site in RoR and call out to your python scraper-scripts may be an option to consider. -- http://mail.python.org/mailman/listinfo/python-list
