My solution to the lack of graphics is ipython or a workflow that looks like it - a loop that renders charts, runs code and places results in a markdown file, then rendered in the browser.
That's about as live as you can get mixing Windows and open source.
On Wed, Sep 28, 2016 at 5:39 PM, Olaf Klinke <olf@aatal-apotheke.de> wrote:* To compete with other recent teaching languages, a really simple GUI library to use within ghci would be fine. (diagrams and GTK?) Quick Basic included "line" and "circle" commands to play with, even though the rest of the language did not prepare me for more advanced languages.
This turns out to be much easier if you assume that Windows and OS X are not worth supporting, or are happy with forcing users on those platforms to jump through annoying hoops (*especially* Windows; there are reasonable ways to get gtk on OS X, even though it doesn't come with the system, but Windows is still the Wild West as far as third party libraries are concerned --- Chocolatey notwithstanding). :/As to the versioning and backward compatibility issues of a standard library: In my eyes the whole concept of version numbers is broken. Dependencies should be stated in terms of type signatures.And ghc in fact uses hashes generated from this. But this has to include the signatures of internals because they can leak out for inlining --- so you still have more problems than other languages do._______________________________________________--brandon s allbery kf8nh sine nomine associatesunix, openafs, kerberos, infrastructure, xmonad http://sinenomine.net
Haskell-Cafe mailing list
To (un)subscribe, modify options or view archives go to:
http://mail.haskell.org/cgi-bin/mailman/listinfo/haskell-cafe
Only members subscribed via the mailman list are allowed to post.