[Haskell-cafe] The Good, the Bad and the GUI

Tom Ellis tom-lists-haskell-cafe-2013 at jaguarpaw.co.uk
Wed Aug 13 23:23:12 UTC 2014


On Thu, Aug 14, 2014 at 01:19:19AM +0200, Wojtek Narczyński wrote:
> On 13.08.2014 23:28, Alexander Vieth wrote:
> >>Oh, please. Haskell is great for parsing, because you can build a parser
> >> with e.g.  parsec, attoparsec, uuparse, trifeca, in no time.  Even I
> >> can do it.  Haskell is great for concurrency, because it has
> >> lightweight threads, STM, and a fabulous book about it.  Haskell is
> >> great for GUIs, because....  how about you finish this statement, I
> >> don't know how to.
>
> >Before parsec, attoparsec, uuparse, et al were invented, was Haskell no
> > good for parsing?  When we speak of Haskell do we speak of the entire
> > ecosystem, or just the language itself?
> 
> It is clear what I meant.
> 
> >I think Heinrich meant that Haskell, the language, is probably capable of
> > carrying a great library for expressing GUI's, even if we haven't yet
> > seen it implemented.
> 
> Haskell, the language, is great for GUIs, because... "(it) is
> probably capable of carrying a great library for expressing GUI's,
> even if we haven't yet seen it implemented." This is too much, I
> need to sleep it off.

Perhaps you could give an example of a language that is "great for GUIs" and
a great functional snippet of GUI code in that language.  Otherwise we're
just discussing in the abstract which tends not to be very helpful.

Tom


More information about the Haskell-Cafe mailing list