tag:blogger.com,1999:blog-4093229006254491664.post3981031663154825627..comments2023-08-03T09:55:23.967-04:00Comments on Biased Estimates: An update on "A Comparison of Programming Languages in Economics"Tommyhttp://www.blogger.com/profile/14573787040201086607noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-4093229006254491664.post-84040962085702072332014-07-25T17:19:56.468-04:002014-07-25T17:19:56.468-04:00I was wondering why you hadn't commented on th...I was wondering why you hadn't commented on the first post, actually. :) <br /><br />I have found that my fastest R code (with some exceptions) is also cleaner to read and follow. That said, R will never be a "fast" language. <br /><br />For further interest in advanced R programming though, check out this site: http://adv-r.had.co.nz/Tommyhttps://www.blogger.com/profile/14573787040201086607noreply@blogger.comtag:blogger.com,1999:blog-4093229006254491664.post-45005431836525789042014-07-25T11:25:28.002-04:002014-07-25T11:25:28.002-04:00(you just know that i'm going to pop up here!)...(you just know that i'm going to pop up here!)<br /><br />interesting stuff.<br /><br />without devaluing the merits of R, pushing R on execution speed is futile. it's just not its thing and you end up with code that's got little tricks all over in an attempt to keep up speed which makes things difficult to follow.<br /><br />matrix and vector ops are not going away but so is writing loops. it's simply much clearer to go ahead and write that in compiled Python, C/C++, Julia, or Fortran.Majid alDosarihttps://www.blogger.com/profile/16192275403547721607noreply@blogger.com