<?xml version="1.0" encoding="UTF-8"?>
<oembed>
 <version>1.0</version>
 <type>link</type>
 <provider_name>Rainbow Dash Network</provider_name>
 <provider_url>http://rainbowdash.net/</provider_url>
 <title>Chris Bell (mrdragon)'s status on Tuesday, 26-Jul-11 13:47:41 UTC</title>
 <author_name>Chris Bell (mrdragon)</author_name>
 <author_url>http://rainbowdash.net/mrdragon</author_url>
 <url>http://rainbowdash.net/notice/321629</url>
 <html>@&lt;span class=&quot;vcard&quot;&gt;&lt;a href=&quot;http://rainbowdash.net/user/2782&quot; class=&quot;url&quot; title=&quot;Giles&quot;&gt;&lt;span class=&quot;fn nickname&quot;&gt;ixfocus&lt;/span&gt;&lt;/a&gt;&lt;/span&gt; It's not the coding. It's the server based backend setup which it comes with. Trying to setup something that's coded in ruby to get it working on a site, is quite hard to say the least. Compaired to sql and tables, I have to work with rubygems first and make sure the needed gems are installed. Then SSH and make sure that the install sheets are there are avaliable, if not then I need to find out why (BIG BIG PAIN). Then I have to make sure it all works on rails. Then I still have the SQL and Tables to get done. Sure Ruby allows for a much wider range of interactions, but it's still a right pain to do.</html>
</oembed>
