Me too. I learned the basics at uni in 2000. Had a few plays since but I really need to get stuck in - I want to get to the point where I understand the fancy s

Me too. I learned the basics at uni in 2000. Had a few plays since but I really need to get stuck in - I want to get to the point where I understand the fancy stuff like Lenses. Beyond the cool stuff I strongly believe it can be really practical and I would like to convince my employer (or any employer!) to seriously consider it for a production system. You can't hire Haskell programmers by the 40ft container-load like you can with Java or C#. You won't need as many Haskell programmers though. And they should get paid accordingly :-) Haskell has a duality: It is a nice "toy". I mean that in a good way - fun to play with, enjoyable to code. But also I can see it being a serious contender for writing Enterprise systems where you need clarity, accuracy and readability of business rules. Haskell functions can extend Enterprise systems in an elegant and powerful way, by adding on rules that are safe because they have no side effects. They can only affect things indirectly through their returned results. This means the basic Enterprise system you ship can be simpler and then you can customize it more easily and with more confidence. I envisage smart non-programmers can probably write the custom business rules as tight Haskell scripts. TL;DR I want to cut the cruft with Haskell!