<story><title>Where does Ruby go from here?</title><url>http://blog.sefindustries.com/the-happiness-manifesto/</url></story><parent_chain><item><author>tmorton</author><text>I think this is a great idea.  The ruby community is a wonderful thing, and part of that is reflected in the technology.&lt;p&gt;However, the original Agile Manifesto was powerful because it made tradeoffs.  &amp;quot;We value X over Y&amp;quot;, even when Y is a valuable thing.  For this HDD thing to take off, it has to make the similar tradeoffs explicit.&lt;p&gt;For example:&lt;p&gt;&lt;pre&gt;&lt;code&gt;  We value readable code over runtime performance.
  We value open-source frameworks and libraries over developing for popular ecosystems.
  We value inclusiveness, diversity, and respect over pure meritocracy.
  We value teaching, learning, and improving our craft over short-term productivity.
  We value creating wealth over capturing wealth.&lt;/code&gt;&lt;/pre&gt;</text></item></parent_chain><comment><author>angersock</author><text>That&amp;#x27;s a really nice feel-good list, but it also doesn&amp;#x27;t make a lot of sense in several cases:&lt;p&gt;&lt;i&gt;&amp;quot;We value open-source frameworks and libraries over developing for popular ecosystems.&amp;quot;&lt;/i&gt;&lt;p&gt;Most popular ecosystems nowadays are all open-source frameworks and libraries? Unless you&amp;#x27;re talking about Windows or Mac OSX, I guess?&lt;p&gt;&lt;i&gt;&amp;quot;We value inclusiveness, diversity, and respect over pure meritocracy.&amp;quot;&lt;/i&gt;&lt;p&gt;These are not mutually exclusive goals--even if they are, I&amp;#x27;d rather have really good code, even if written by a racist or sexist, than bad code (period). Again, I&amp;#x27;m not sure we have to make that choice.&lt;p&gt;&lt;i&gt;&amp;quot;We value creating wealth over capturing wealth.&amp;quot;&lt;/i&gt;&lt;p&gt;What does this even mean? This is a &lt;i&gt;programming language&lt;/i&gt;, ffs. Your statement makes sense in, say, the heyday of APL or Smalltalk or some other very vendor-specific language, but that&amp;#x27;s not quite the case today. Are you talking about &lt;i&gt;not&lt;/i&gt; doing data-mining to monetize your fellow man? About not creating yet-another analytics or ad platform? What then, exactly, are you driving at?&lt;p&gt;&lt;i&gt;&amp;quot;We value teaching, learning, and improving our craft over short-term productivity.&amp;quot;&lt;/i&gt;&lt;p&gt;Again, not mutually exclusive. Also, part of learning and improving your craft is knowing when a quick hack is the right answer instead of a full solution.</text></comment>
<story><title>Where does Ruby go from here?</title><url>http://blog.sefindustries.com/the-happiness-manifesto/</url></story><parent_chain><item><author>tmorton</author><text>I think this is a great idea.  The ruby community is a wonderful thing, and part of that is reflected in the technology.&lt;p&gt;However, the original Agile Manifesto was powerful because it made tradeoffs.  &amp;quot;We value X over Y&amp;quot;, even when Y is a valuable thing.  For this HDD thing to take off, it has to make the similar tradeoffs explicit.&lt;p&gt;For example:&lt;p&gt;&lt;pre&gt;&lt;code&gt;  We value readable code over runtime performance.
  We value open-source frameworks and libraries over developing for popular ecosystems.
  We value inclusiveness, diversity, and respect over pure meritocracy.
  We value teaching, learning, and improving our craft over short-term productivity.
  We value creating wealth over capturing wealth.&lt;/code&gt;&lt;/pre&gt;</text></item></parent_chain><comment><author>kybernetyk</author><text>&amp;gt;   We value inclusiveness, diversity, and respect over pure meritocracy.&lt;p&gt;Heh, until not long ago a &amp;quot;meritocracy&amp;quot; was seen as something good and desirable. Nowadays it seems to be something bad (at least in some circles). Funny how things can change.</text></comment>