Haskell at least is good a specifying what some code CANNOT do. This is nice for instance in order to know if you can safely retry an operation in a transactional section or whether some function is thread-safe.
Expressivity without losing too much readability is also a big win.
>>52401891 It's not that the code is shitty, it's that most programmers don't learn about functional programming. They're python babies who barely understand C. You write some helper programs in Haskell for your main projects and you've given yourself job security because odds are you're one of the only ones in the company who bothered to learn how to use it. So everything goes wrong if they don't keep someone on the job who can maintain the helper programs.
All trademarks and copyrights on this page are owned by their respective parties. Images uploaded are the responsibility of the Poster. Comments are owned by the Poster.
This is a 4chan archive - all of the shown content originated from that site. This means that 4Archive shows their content, archived. If you need information for a Poster - contact them.
If a post contains personal/copyrighted/illegal content, then use the post's [Report] link! If a post is not removed within 24h contact me at firstname.lastname@example.org with the post's information.