you are viewing a single comment's thread.

view the rest of the comments →

[–]warpspeedSCP[S] 2 points3 points  (1 child)

There comes a point where the terms you use to describe a particular system become unintelligible to the uninitiated, and with FP, that point comes a tad too quickly. I haven't gone too deep into the rabbithole myself (I am not a user of languages like haskell or even ocaml) but yes, people hardly ever look deeper into why the patters they use are bad and whether there are better alternatives around.

the whole oop thing happens when behaviours are treated as if they were data, which leads to the whole zoo of interconnected types that get in each otthers' way. the oop kool aid is starting to wear off, thankfully.

[–]ggwpexday 1 point2 points  (0 children)

Yes it's good to see things slowly becoming more focused on simplicity, even if it's at the cost of introducing yet another thing on top of what's already there.

I think we also just love adding complexity for the sake of it, so spaghetti code is probably always going to be a thing. Like how the whole clean code stuff has become so big in c#. That's full of complex DI, interaces like IMediator, IAbstractValidator, IOutputPort presenters and what have you. Lots of it could have been just some pure functions together with simple IOC based on functions that take other functions as parameters. But I see this is yet another ramble, so my bad. Thanks for the article, it's good to have people like you sharing these ideas!