24 Mar '12, 3pm

@tdkn_ と同じ現象かも。gem_prelude.rbを廃止する提案が出て、問題が起こる、となってます。 には廃止した影響が載ってますね。RubyGems 1.8.19では廃止されてるっぽい。

I think it is time for gem_prelude to die. It was created to address a symptom, namely, that rubygems was slow on some systems (and proportional to the number of gems you have installed). I don't know of any other reason why it exists. If there are other reasons, I'd like to know. The problem with dealing with symptoms instead of core problems is that you wind up with a bandaid on a bandaid and eventually you get bogged down. The rubygems team is bogged down and the release of 1.4 shows that 1.9.2's gem_prelude is a serious problem that needs to be addressed quickly. The speed issues have been addressed by: + `require`ing a lot less globally and only `require`ing as needed. [*] + Not loading plugins by default. + Version comparisons have been optimized. (thanks Aman!) I'd like to drop gem_prelude down to 'require "rubygems"'. If you want, we can profile this against normal...

Full article: http://www.ruby-forum.com/topic/799158


integrating PHP and Ruby On Rails - Ruby Forum

ruby-forum.com 24 Mar '12, 7am

check out if they have a REST-api and access this API using one of the numerous tools available like ActiveResource or Htt...