Explore >> Select a destination
|
You are here 
|
jackkelly.name | ||
| | | | |
julesh.com
|
|
| | | | | Geometry of Interaction (also known as the Int-construction) is an important construction in category theory that shows up the semantics of concurrency. It's also a contender for my favourite thing in category theory. It's one member of a whole zoo of things that look kinda like lenses but are a bit different. Back around 2017... | |
| | | | |
bartoszmilewski.com
|
|
| | | | | I always believed that the main problems in designing a programming language were resource management and concurrency--and the two are related. If you can track ownership of resources, you can be sure that no synchronization is needed when there's a single owner. I've been evangelizing resource management for a long time, first in C++, and... | |
| | | | |
bartoszmilewski.com
|
|
| | | | | For an outsider, Haskell is full of intimidating terms like functor, monad, applicative, monoid... These mathematical abstractions are hard to explain to a newcomer. The internet is full of tutorials that try to simplify them with limited success. The most common simplification you hear is that a functor or a monad is like a box... | |
| | | | |
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? | ||
