<?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>loveydoe's status on Friday, 08-Aug-14 16:18:01 UTC</title>
 <author_name>loveydoe</author_name>
 <author_url>http://rainbowdash.net/loveydoe</author_url>
 <url>http://rainbowdash.net/notice/3579784</url>
 <html>@&lt;span class=&quot;vcard&quot;&gt;&lt;a href=&quot;http://rainbowdash.net/user/28563&quot; class=&quot;url&quot; title=&quot;ryanjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjj&quot;&gt;&lt;span class=&quot;fn nickname mention&quot;&gt;l1ghtsword&lt;/span&gt;&lt;/a&gt;&lt;/span&gt; I find that boiling code down to functions with few side-effects makes things cleaner.  OOP is necessary sometimes, but in certain projects, like Synfig Studio, it is used too much.  For example, there is a whole class for cosine, which mostly just contains code that runs cos, the actual function for cosine, but I think it was made into a class so that it can be grouped with similar functions into an array of Value Node functions.  Places like that drive me away from OOP.  &lt;i&gt;But&lt;/i&gt;, holy wars have been fought over this very topic; OOP is a wonderful thing, especially to programmers who use it.  I will stick with my functions and subroutines.</html>
</oembed>
