I used Haskell on my every job last 12 years to quickly prototype various things to get problems exposed early. This included: prototypes of image analyses (im

I used Haskell on my every job last 12 years to quickly prototype various things to get problems exposed early. This included: prototypes of image analyses (image registration), MIPS-alike CPU prototype, Direct3D pixel/vertex shader assembler language analysis (data flow patterns), prototyping various dynamic data flow CPUs, translator Fortran-to-Lisp (for our colleague who prototyped compiler analysis in Lisp), testbed for viodecontroller, VHDL-to-netlist translator (synthesable subset) for our modeling system, simple GUI for some kind of IDE for modeling system, DSeL for CPU model description. I even tried to create integrator for "game physics" using infinite lazy lists using ideas from http://citeseerx.ist.psu.edu/viewdoc/summary?doi=10.1.1.32.4535 http://citeseerx.ist.psu.edu/viewdoc/summary?doi=10.1.1.32.4... Most of my pet projects start as a Haskell source. Often they get abandoned, sometimes they evolve into something big. This "pettiness" of Haskell projects play an important role: they can be thrown away because they are cheap, and they can evolve into something pretty big - easily.