<story><title>State of the Haskell Ecosystem – February 2016</title><url>http://www.haskellforall.com/2016/02/state-of-haskell-ecosystem-february.html?m=1</url></story><parent_chain><item><author>dexwiz</author><text>Can someone explain to me why Haskell will ever be viable as  a fullstack language? I have done a few toy projects in Haskell, and it has taught me some great functional programming concepts that I now apply to other languages. But, purely functional programming seems to work 90% the time, but the other 10% is so negative it invalidates the rest.&lt;p&gt;&lt;i&gt;&lt;/i&gt;Edit for clarification:
Full Stack would be app server up. So runs a server (some sort of process&amp;#x2F;thread&amp;#x2F;worker management), server scripting is in the same language (can auth, process requests, interact with a DB, etc), and build the view (simple JSON&amp;#x2F;blob response, build html, etc). I exclude client side form this, since most of the X for client-side projects end up transpiling into JS.</text></item></parent_chain><comment><author>tathougies</author><text>I use Haskell exclusively on my SaaS app (&lt;a href=&quot;http:&amp;#x2F;&amp;#x2F;sostenoto.com&quot; rel=&quot;nofollow&quot;&gt;http:&amp;#x2F;&amp;#x2F;sostenoto.com&lt;/a&gt;). The backend not only provides a simple REST API, but it also provides WebRTC signaling and a real-time graphical communications and presence protocol.&lt;p&gt;Haskell makes it so easy to write correct concurrent code it&amp;#x27;s not even funny. GHC&amp;#x27;s magnificent IO manager means I can handle 1000s of connections on one amazon instance. Can&amp;#x27;t understand why you wouldn&amp;#x27;t be using Haskell for server-side web development.&lt;p&gt;No other popular server-side language supports concurrency (see STM, MVar&amp;#x27;s, and Chans), transparent futures&amp;#x2F;promises for I&amp;#x2F;O (the entire IO monad in GHC is non-blocking), support for multiple processors (Just add +RTS -N&amp;lt;n&amp;gt; to make your program scale to n processors), and a blazing fast HTTP server (warp).</text></comment>
<story><title>State of the Haskell Ecosystem – February 2016</title><url>http://www.haskellforall.com/2016/02/state-of-haskell-ecosystem-february.html?m=1</url></story><parent_chain><item><author>dexwiz</author><text>Can someone explain to me why Haskell will ever be viable as  a fullstack language? I have done a few toy projects in Haskell, and it has taught me some great functional programming concepts that I now apply to other languages. But, purely functional programming seems to work 90% the time, but the other 10% is so negative it invalidates the rest.&lt;p&gt;&lt;i&gt;&lt;/i&gt;Edit for clarification:
Full Stack would be app server up. So runs a server (some sort of process&amp;#x2F;thread&amp;#x2F;worker management), server scripting is in the same language (can auth, process requests, interact with a DB, etc), and build the view (simple JSON&amp;#x2F;blob response, build html, etc). I exclude client side form this, since most of the X for client-side projects end up transpiling into JS.</text></item></parent_chain><comment><author>jkxyz</author><text>Care to elaborate on what the 10% covers? I can see a few places where pure functional programming might not be as clear as imperative code, but I don&amp;#x27;t think that it invalidates the possibility of using it for large projects.</text></comment>