3 ms·
> One of the biggest issues with this pattern is if there's a ton of IO that's necessary for the application. Yes, that's why patterns like this are necessary.
by mrkeen 3y ago
> One of the biggest issues with this pattern is if there's a ton of IO that's necessary for the application.
Yes, that's why patterns like this are necessary.
Do you stop doing dependency inversion when you have too many dependencies?
- corethree 3y agoYou're not getting it. When there's so much IO, which is what happens in a lot of web applications, most of your code isn't going to be pure anyway. Even your haskell code under do-notation looks very procedural because there's just so much IO. So you're basically back to programming regular code. It doesn't solve the core problem. The pattern itself is good and is not a problem and I believe the pattern that should be followed.... but in the end practically speaking for the web it doesn't do too much to remove the main issue.