{"version":"1.0","provider_name":"Rainbow Dash Network","provider_url":"http:\/\/rainbowdash.net\/","type":"link","title":"loveydoe's status on Friday, 08-Aug-14 16:18:01 UTC","author_name":"loveydoe","author_url":"http:\/\/rainbowdash.net\/loveydoe","url":"http:\/\/rainbowdash.net\/notice\/3579784","html":"@<span class=\"vcard\"><a href=\"http:\/\/rainbowdash.net\/user\/28563\" class=\"url\" title=\"ryanjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjj\"><span class=\"fn nickname mention\">l1ghtsword<\/span><\/a><\/span> 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.  <i>But<\/i>, 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."}