4 ms·

“Best practices should be easy” is the corollary which, unfortunately, we are a long ways off from with Haskell itself, lending programmers to continue to use P

• deleted 5y ago
  [deleted]
• Tanjreeve 5y ago
  The end goal of a software project isnt just to write some code it's to write an effective application that's valuable to the business (aka it's supportable and iterable and all that businessy stuff). It's very easy to write some code in Python but very hard to know that it's correct without huge amounts of testing. And if you have changes happening on an application it's much harder to know your change hasn't affected something else when your main route is writing huge amounts of tests (that can also break). A language that falls over at compile time when it's passing wrong types means your potential avenues for mistakes are already hugely narrowed down to business logic. If your application functionality is kept on course more then you're less likely to descend into chaos and find yourself paying a load of expensive Devs to chase down stupid bugs and debugging to keep things working rather than doing valuable "new" work. Another benefit is if you can refactor with confidence you can expand functionality easier and not find yourself written into a corner by prohibitive Dev time costs.