3 ms·
Close. I'm more asking if there has been study into ways of plugging the different paradigms together into a whole solution. That is, I firmly believe that ea
by taeric 13y ago
Close. I'm more asking if there has been study into ways of plugging the different paradigms together into a whole solution. That is, I firmly believe that each have their strengths. To carry a sports analogy through to this, teams practice different strategies and techniques in isolation so that together they can operate better. Seems most of the reading is about this isolated level of practice. I would love a more holistic view that covers it all.
Edit: So, monads help show what happens under the scenes for when you are writing imperatively, but they do little to illuminate when that style is beneficial. My contention is that this is up to the metaphors one has defined for their program.
- breckinloggins 13y agoMe too. I have a personal "research hobby" aimed at exactly this. For your monads example: one of the things I'm looking into is how to have the experts establish the monadic abstraction and have the system gain all of the benefit WITHOUT jRandomCoder at HugeCorp having to understand what a monad is... or even realize he's using one. Obviously Haskell falls short in that area.
- runT1ME 13y ago> or even realize he's using one. Uh, this happens all the time. Scala programmers everywhere are used to the pattern for { a <- optionA b <- optionB } yield ("Both options have values! A = " + a + " B ="+b)