Explore >> Select a destination
|
You are here 
|
cronokirby.com | ||
| | | | |
bartoszmilewski.com
|
|
| | | | | In the previous instalment of Category Theory for Programmers we talked about the category of types and functions. If you're new to the series, here's the Table of Contents. You can get real appreciation for categories by studying a variety of examples. Categories come in all shapes and sizes and often pop up in unexpected... | |
| | | | |
www.jeremykun.com
|
|
| | | | | A lot of people who like functional programming often give the reason that the functional style is simply more elegant than the imperative style. When compelled or inspired to explain (as I did in my old post, How I Learned to Love Functional Programming), they often point to the three "higher-order" functions map, fold, and filter, as providing a unifying framework for writing and reasoning about programs. But how unifying are they, really? | |
| | | | |
argumatronic.com
|
|
| | | | | Occasional writings about Haskell. | |
| | | | |
fsharpforfunandprofit.com
|
|
| | | [AI summary] The article argues that F# is the best enterprise language due to its suitability for enterprise development's constraints and demands, such as long project lifecycles, maintenance, and stability. It highlights the importance of static typing, immutability, and functional programming principles in enhancing productivity and maintainability. The author also discusses the challenges of adopting new technologies in enterprises and evaluates various languages like Java, C#, Kotlin, and TypeScript, ultimately favoring F# for its comprehensive support and functional-first approach. | ||
