/explore
|
You are here 
|
blog.ploeh.dk | ||
| | | | |
theartofmachinery.com
[AI summary] A software engineering article argues that relaxing the strict definition of pure functions into 'weak purity' can significantly improve code testability, error handling, and modularity in imperative languages like C++, Java, and Python without losing the core benefits of functional design. |
|
| | | | | ||
| | | | |
ashishvegaraju.com
In my last article about Functional domain modeling, I explored the expressiveness of F# in modeling a domain. I fell in love with the simplicity and expressiveness of the language. In this article I will attempt to explore function purity in F#. In F#, functions are first class citizens because it allows to pass function as an argument to other function, return a function or assign function to a variable. Initially I found it a bit hard to wrap my head around the concept of treating functions as first class citizens. In fact one of the biggest challenge for me was surprisingly not the weird syntax of F#, but to think in terms of functions. |
|
| | | | | ||
| | | | |
degoes.net
Effect tracking is not a non-goal for commercial software development; the real reasons to use functional effect systems lie elsewhere |
|
| | | | | ||
| | | | |
blog.jetbrains.com
Rust and Java couldn't be any more different. One is a battle-tested giant with enterprise-scale use cases. The other is a relative newbie with a rapidly growing community and real-world applications. |
|
| | | |||
