Please log in to watch this conference skillscast.
I had a bug in my embedded lazy Scheme interpreter and couldn't figure it out in F#, so I did what I typically do when lost: prototype in Haskell.
After a complete conversion/rewrite from F# into Haskell, all known bugs were gone.
One of the biggest features of Haskell turns out to be the equational nature that allows writing and thinking with greater modularity.
Haskell isn't perfect for every use case — but it's a great way to really get clear on your thinking about a problem space.
In the Q&A session of this talk, an audience member requests that Andre make public the repositories for his project (Plotting and Scheming). You can find both the Haskell and F# repositories, here: https://github.com/avanmeul
YOU MAY ALSO LIKE:
- Functional Concurrency in .NET with C# and F# with Riccardo Terrell (Online Workshop on 11th - 14th October 2022)
- F# eXchange 2022: Online (Online Conference on 25th - 26th October 2022)
- F# eXchange 2022: In-Person (in London on 25th - 26th October 2022)
- Haskell: Why and How the External STG Interpreter is Useful (SkillsCast recorded in December 2021)
- Keynote — Haskell: What To Do When Success Can't Be Avoided (SkillsCast recorded in November 2021)
Haskell: A Conversion Experience
I was introduced to functional programming (FP) through university coursework in the 80s that involved LISP.
I've been sold on FP ever since, and wish to contribute to the success of Haskell (and other FP languages) in the real world; so that FP languages can be more viable for both home and professional use.
For pragmatic reasons, I have largely used conventional languages professionally, and used FP mostly for home use.
My home project involving conversion of an F# project to Haskell also caused an unexpected internal conversion: I now love Haskell so much I want to fully transition to Haskell for all programming (both at home and professionally).
In my talk, I wish to explore the advantages of Haskell, while also being honest about its challenges.