Originally posted by Electric-Gecko
View Post
Originally posted by Electric-Gecko
View Post
That said, Haskell is a language worth knowing even if you're not intending to ever use it. If your coding skills are in stage where you can embody simple algorithms in code, but struggle to architect apps the right way, e.g. your code is full of global variables, awkward error handling, race conditions, and you struggle to see the time to break a function — it's time to learn some Haskell. The language forces you into better design, it teaches you some generic style that you can later apply in any language.
For example, from just C/C++ background, function pointers was always looking like odd beasts to me, I'd hardly ever use them, except as if the algorithm jumped at me screaming "use a function pointer FFS!" (well, it was 2-3 years ago, I didn't know about C++14 closures back then). But in Haskell they're as natural as they can be, so after you get back from Haskell to C/C++, you'd just start seeing patterns where function pointer can make your life much easier. (that said, back then I didn't even hear about Haskell, and learned the same thing from elisp, but both langs treating functions in alike manner, so it doesn't really matter)
Comment