<story><title>Why Fogbugz lost to Jira</title><url>http://movingfulcrum.com/why-fogbugz-lost-to-jira/</url></story><parent_chain><item><author>outworlder</author><text>An interesting point from that, since everyone likes to bash Wasabi:&lt;p&gt;&amp;gt; &amp;quot;If we hadn&amp;#x27;t done Wasabi, then we&amp;#x27;d have had to rewrite all of FogBugz, and that would&amp;#x27;ve killed the company. Wasabi also gave us stuff that developers are only now rediscovering, like code that executes on both client and server (e.g. via server-side&amp;#x2F;client-side React), that even gave us a development edge. I&amp;#x27;ve written about this at length (&lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;news.ycombinator.com&amp;#x2F;item?id=9779133&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;news.ycombinator.com&amp;#x2F;item?id=9779133&lt;/a&gt;) and won&amp;#x27;t revisit it, but while I think that Wasabi targeting .NET may have been a mistake, Wasabi itself was not a mistake.&amp;quot;</text></item><item><author>JimDabell</author><text>There&amp;#x27;s an interesting discussion happening on Reddit involving ex-employees of both companies:&lt;p&gt;&lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;www.reddit.com&amp;#x2F;r&amp;#x2F;programming&amp;#x2F;comments&amp;#x2F;3n2sc1&amp;#x2F;why_fogbugz_lost_to_jira&amp;#x2F;&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;www.reddit.com&amp;#x2F;r&amp;#x2F;programming&amp;#x2F;comments&amp;#x2F;3n2sc1&amp;#x2F;why_fog...&lt;/a&gt;</text></item></parent_chain><comment><author>glass-</author><text>This blog post about Wasabi is worth a read (another perspective from someone who worked there): &lt;a href=&quot;http:&amp;#x2F;&amp;#x2F;www.tedunangst.com&amp;#x2F;flak&amp;#x2F;post&amp;#x2F;technical-debt-and-tacking-into-the-wind&quot; rel=&quot;nofollow&quot;&gt;http:&amp;#x2F;&amp;#x2F;www.tedunangst.com&amp;#x2F;flak&amp;#x2F;post&amp;#x2F;technical-debt-and-tacki...&lt;/a&gt;</text></comment>
<story><title>Why Fogbugz lost to Jira</title><url>http://movingfulcrum.com/why-fogbugz-lost-to-jira/</url></story><parent_chain><item><author>outworlder</author><text>An interesting point from that, since everyone likes to bash Wasabi:&lt;p&gt;&amp;gt; &amp;quot;If we hadn&amp;#x27;t done Wasabi, then we&amp;#x27;d have had to rewrite all of FogBugz, and that would&amp;#x27;ve killed the company. Wasabi also gave us stuff that developers are only now rediscovering, like code that executes on both client and server (e.g. via server-side&amp;#x2F;client-side React), that even gave us a development edge. I&amp;#x27;ve written about this at length (&lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;news.ycombinator.com&amp;#x2F;item?id=9779133&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;news.ycombinator.com&amp;#x2F;item?id=9779133&lt;/a&gt;) and won&amp;#x27;t revisit it, but while I think that Wasabi targeting .NET may have been a mistake, Wasabi itself was not a mistake.&amp;quot;</text></item><item><author>JimDabell</author><text>There&amp;#x27;s an interesting discussion happening on Reddit involving ex-employees of both companies:&lt;p&gt;&lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;www.reddit.com&amp;#x2F;r&amp;#x2F;programming&amp;#x2F;comments&amp;#x2F;3n2sc1&amp;#x2F;why_fogbugz_lost_to_jira&amp;#x2F;&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;www.reddit.com&amp;#x2F;r&amp;#x2F;programming&amp;#x2F;comments&amp;#x2F;3n2sc1&amp;#x2F;why_fog...&lt;/a&gt;</text></item></parent_chain><comment><author>zem</author><text>i thought wasabi was an excellent idea when i first read spolsky&amp;#x27;s post about it, and nothing i&amp;#x27;ve heard since has changed my mind. these days, when i see it blamed for any of fogcreek&amp;#x27;s problems, i simply see it as a sign that the commenter is unfamiliar with the issues involved.</text></comment>