After using Haskell, using Java makes me very sad... In Java's OO paradigm, instance variables are inherently defined separately from their initialization, mak

After using Haskell, using Java makes me very sad... In Java's OO paradigm, instance variables are inherently defined separately from their initialization, making it quite difficult to make sure they're always used when initialized, properly. The nullability stuff bites me over and over :( Forgetting to use .start() on a thread is a stupid runtime error, instead of using some design where it isn't possible to forget .start() or at least get a compile-time error. I am also using a lot of C in parallel, and with the C preprocessor, I am finding that C is often more expressive and nicer to use than Java! Everything takes ridiculous amounts of code. For example, in Haskell, I can write: threadIds <- replicateM 10 . forkIO . forever $ do code .. here .. To get a thread-pool of 10 threads looping around my code, and put their thread ids in a variable. In Java, this requires so much effort! Not to mention the utter lack of sum types and pattern-matching, making tons of Java code that looks like: if(msg.what == Foo) { msg.obj1 ... msg.obj2 ... } else if(msg.what == Bar) { .. } arrrg!