<?xml version="1.0" encoding="utf-8"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>statistically incorrect - Latest Comments</title><link>http://statistically-incorrect.disqus.com/</link><description></description><atom:link href="https://statistically-incorrect.disqus.com/comments.rss" rel="self"></atom:link><language>en</language><lastBuildDate>Mon, 22 Feb 2021 04:55:10 -0000</lastBuildDate><item><title>Re: Object composition implementation styles</title><link>http://anomalizer.net/statistically-incorrect/2011/12/object-composition-2/#comment-5278257599</link><description>&lt;p&gt;that is the best thing I've ever seen. thank you&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">oxbord</dc:creator><pubDate>Mon, 22 Feb 2021 04:55:10 -0000</pubDate></item><item><title>Re: Object composition implementation styles</title><link>http://anomalizer.net/statistically-incorrect/2011/12/object-composition-2/#comment-5152408954</link><description>&lt;p&gt;aa&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">hi</dc:creator><pubDate>Sun, 15 Nov 2020 06:39:35 -0000</pubDate></item><item><title>Re: &amp;#8220;Server side&amp;#8221; languages in 2012</title><link>http://anomalizer.net/statistically-incorrect/2013/01/server-side-languages-in-2012/#comment-2985774482</link><description>&lt;p&gt;Yes&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">John Jones</dc:creator><pubDate>Sat, 05 Nov 2016 01:13:20 -0000</pubDate></item><item><title>Re: What the hell is dependency injection?</title><link>http://anomalizer.net/statistically-incorrect/2013/08/dependency-injection-intro/#comment-2512576881</link><description>&lt;p&gt;Thank you. This makes sense.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">pk</dc:creator><pubDate>Sat, 13 Feb 2016 23:02:57 -0000</pubDate></item><item><title>Re: Pointer internals reinvented: Go</title><link>http://anomalizer.net/statistically-incorrect/2014/01/pointer-internals-golang/#comment-1189003945</link><description>&lt;p&gt;Nope. A go pointer to a primitive type would always contain 2 things: (1) actual memory address of the primitive (2) a pointer to the vtable of the primitive type. Put it another way, a pointer to primitive is no different from a pointer to a struct.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">anomalizer</dc:creator><pubDate>Mon, 06 Jan 2014 08:24:40 -0000</pubDate></item><item><title>Re: Pointer internals reinvented: Go</title><link>http://anomalizer.net/statistically-incorrect/2014/01/pointer-internals-golang/#comment-1188996985</link><description>&lt;p&gt;Apologies for the same. Will have the edits.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">anomalizer</dc:creator><pubDate>Mon, 06 Jan 2014 08:15:15 -0000</pubDate></item><item><title>Re: Pointer internals reinvented: Go</title><link>http://anomalizer.net/statistically-incorrect/2014/01/pointer-internals-golang/#comment-1185334457</link><description>&lt;p&gt;May be I'm missing something, but how does use of two pointers instead of one eliminate the need for boxed variants? The fundamental issue of whether to treat the next 4/8 bytes as a value or as a pointer to memory still remains, doesn't it?&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Lakshman Kakkirala</dc:creator><pubDate>Fri, 03 Jan 2014 08:15:27 -0000</pubDate></item><item><title>Re: Pointer internals reinvented: Go</title><link>http://anomalizer.net/statistically-incorrect/2014/01/pointer-internals-golang/#comment-1183912952</link><description>&lt;p&gt;I hate to say this, but trailing proof-reading as-you-write might have helped quite a bit. I could not even understand a few lines because of typos or other randomness in the writing. Case in point: "the concept there was fairly simply; the only the a pointer was expected to". WTF :-)&lt;/p&gt;&lt;p&gt;Otherwise, interesting. I am starting Go this year as well. Not close to production level, but at least Project Euler.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Tejaswi Nadahalli</dc:creator><pubDate>Thu, 02 Jan 2014 00:06:21 -0000</pubDate></item><item><title>Re: Languages &amp;#038; IDEs; what begets what</title><link>http://anomalizer.net/statistically-incorrect/2013/10/language-ide-what-begets-what/#comment-1078412905</link><description>&lt;p&gt;I use PyCharm IDE for Python, and I'm finding it hard to let go of it and go to Emacs; PyCharm does a lot of the IDE things that is expected for static typing languages.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Swaroop</dc:creator><pubDate>Thu, 10 Oct 2013 23:20:37 -0000</pubDate></item><item><title>Re: &amp;#8220;Server side&amp;#8221; languages in 2012</title><link>http://anomalizer.net/statistically-incorrect/2013/01/server-side-languages-in-2012/#comment-758684022</link><description>&lt;p&gt;Go Java?&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Siddharth Misra</dc:creator><pubDate>Mon, 07 Jan 2013 04:27:32 -0000</pubDate></item><item><title>Re: Implications of object composition styles</title><link>http://anomalizer.net/statistically-incorrect/2011/10/object-composition/#comment-561033401</link><description>&lt;p&gt;Nice abstract post!&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Avi Dullu</dc:creator><pubDate>Mon, 18 Jun 2012 10:34:07 -0000</pubDate></item><item><title>Re: Why you can&amp;#8217;t always just throw more hardware at it</title><link>http://anomalizer.net/statistically-incorrect/2009/02/throwing-in-more-hardware-is-not-panacea/#comment-587927821</link><description>&lt;p&gt;Nice.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">mayur</dc:creator><pubDate>Wed, 10 Feb 2010 16:54:33 -0000</pubDate></item><item><title>Re: Why you can&amp;#8217;t always just throw more hardware at it</title><link>http://anomalizer.net/statistically-incorrect/2009/02/throwing-in-more-hardware-is-not-panacea/#comment-587927817</link><description>&lt;p&gt;The "throw more hardware" issue is slowly becoming less of a problem as server farms are finally being called expensive (imagine that) and need to get lean.&lt;br&gt;Also, it seems we are reaching a sort of inflection point between "enough hardware" and "too much information still waiting to be processed".&lt;/p&gt;&lt;p&gt;Case in point, Facebook's recent launch of HipHop for PHP that allwas for faster and nimbler code.&lt;/p&gt;&lt;p&gt;Of course, it does not solve the basic problem of bloatware that you described, but I'm hoping it is a start.&lt;/p&gt;&lt;p&gt;Like everything else, this problem and it's solution seem cyclical&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Vinit</dc:creator><pubDate>Mon, 08 Feb 2010 04:53:54 -0000</pubDate></item></channel></rss>