Functional Programming for the Long Haul
- 2019-01-07 02:00 AM
How do you decide whether a programming language is worth using or not? By necessity, such decisions are usually based on assessments that can be made relatively quickly: the ease of using the language, how productive you feel in the first week, and so on. Unfortunately, this tells us very little about the costs involved in continuing to maintain a project past that initial phase. And in reality, the vast majority of time spent on most projects is spent in those later phases.
Aiodex’s Referral Program will give you 20% -80% commission from their transaction fee for 7 years. The value will be calculated starting from the date the member you invite sign up ☞ https://aiodex.com/p/referral-program
Next Generation Shorten Platform. Optimal choice to make a profit and analyze traffic sources on the network. Shorten URLs and earn big money ☞ http://vrl.to/
Get Free 15 Geek ☞ https://geekcash.org/
Playlists Video Tutorial ☞ http://on.edupioneer.net/7cd1499b1f
Developers Chat Channel ☞ https://discord.gg/KAe3AnN
Learn to code for free and get a developer job ☞ https://codequs.com
I’m (Michael Snoyman) going to claim, based on my own experience and analysis of language features, that functional programming in general, and Haskell in particular, are well suited for improving this long tail of projects. We need languages and programming techniques that allow broad codebase refactorings, significant requirements changes, improving performance in hotspots of the code, and reduced debug time. I believe Haskell checks these boxes.
Original video source: https://www.youtube.com/watch?v=DdR9q69se-I