<div dir="ltr"><div><div><div><div><div>The choice boils down to whether you want stack to manage your GHC installation or not. <br><br>I personally find it distasteful. This has been the biggest blocker for me using stack, it wants to control more of my workflow than I want to give it, leading to an overlap of responsibilities. (I do use stack, but only with external GHC installations, and I often get into a mess when it tries to download another GHC)</div></div></div><br></div><div>Having said that, is it better for new users to delegate the GHC installation to stack? I don't know. It certainly has the downside that you can't just type "ghci" and get a prompt.<br><br></div><div>The world seems simpler when it consists of<br></div>- GHC installations<br><div>- build tools that use your GHC installations and manage local package building<br><br></div><div>But when my build tool manages my GHC installations, there's now a layer of abstraction in the way of GHC and I can't figure out how to interact directly with GHC any more. Also I can't use cabal (which I often do).<br></div><br></div>So, I'd argue for HP minimal to be the default download option. By all means recommend stack as the default build tool - I'm sure it's less problematic for most people to get Stackage by default, and cabal isn't set up to use Stackage out of the box.<br><div><div><br></div><div>Can't we get rid of HP Full? I don't see a use for that any more.<br></div><div><br></div><div>Cheers<br></div><div>Simon<br></div><div><br></div></div></div><div class="gmail_extra"><br><div class="gmail_quote">On 29 August 2016 at 16:29, Nicolas Wu <span dir="ltr"><<a href="mailto:nicolas.wu@gmail.com" target="_blank">nicolas.wu@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Hello,<div><br></div><div>I think having multiple options is confusing to beginners, and so I'd like to see<span style="line-height:1.5"> a single download option on the download page.</span><span style="line-height:1.5"> </span></div><div><br></div><div>For me it's important that we have a way for beginners to use tools like ghc and ghci on the command line directly in order to run small throw-away programs.</div><div><br></div><div>The decision about how to manage projects and their dependencies should be open and isn't for beginners, whether that be using stack or cabal: both have their merits, and I don't want to push one over the other. The default installation should provide both of these as well as other tools core to building ghc.</div><div><br></div><div>As such, I'm in favour of having the HP as the only option.</div><div><br></div><div>Nick</div><div dir="ltr"><div><br></div><div><div class="gmail_quote"><div><div class="h5"><div dir="ltr">On Sat, Aug 27, 2016 at 5:50 AM Jason Dagit <<a href="mailto:dagitj@gmail.com" target="_blank">dagitj@gmail.com</a>> wrote:<br></div></div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div class="h5"><div dir="ltr">Hello all,<div><br></div><div>I just realized that the Minimal installer listed first on the Downloads page (<a href="https://www.haskell.org/downloads" target="_blank">https://www.haskell.org/<wbr>downloads</a>) is deprecated and "dead". This creates an unfortunate situation where our top suggested way to get haskell immediately tells the user it's dead.</div><div><br></div><div>I think that we should remove mention of the minimal installer ASAP on the grounds that the HP now comes in minimal and full variants.</div><div><br></div><div>Furthermore, I would like to make the recommendation that we list the HP above other methods as even the minimal HP installer ships with stack (at least on windows it does).</div><div><br></div><div>Between the two changes, I think the first one is crucial and the second one is merely reasonable.</div><div><br></div><div>Thanks,</div><div>Jason</div><div><br></div><div><br></div></div></div></div><span class="">
______________________________<wbr>_________________<br>
Haskell-community mailing list<br>
<a href="mailto:Haskell-community@haskell.org" target="_blank">Haskell-community@haskell.org</a><br>
<a href="http://mail.haskell.org/cgi-bin/mailman/listinfo/haskell-community" rel="noreferrer" target="_blank">http://mail.haskell.org/cgi-<wbr>bin/mailman/listinfo/haskell-<wbr>community</a><br>
</span></blockquote></div></div></div></div>
<br>______________________________<wbr>_________________<br>
Haskell-community mailing list<br>
<a href="mailto:Haskell-community@haskell.org">Haskell-community@haskell.org</a><br>
<a href="http://mail.haskell.org/cgi-bin/mailman/listinfo/haskell-community" rel="noreferrer" target="_blank">http://mail.haskell.org/cgi-<wbr>bin/mailman/listinfo/haskell-<wbr>community</a><br>
<br></blockquote></div><br></div>