I like a lot of the concepts of FP, but once you get past the "new shiny" aspect of it and start writing applications, the warts start to show. It's really lik

I like a lot of the concepts of FP, but once you get past the "new shiny" aspect of it and start writing applications, the warts start to show. It's really like anything - extreme/purist FP can have terrible application performance with limited benefit. Same with extreme/purist OOP. JS classes hit a sweet spot for me. They are minimalist, composable, easy to duck-type, and are basically just a convenient unit of code organization more than anything. I never really jumped on the "pure fp" bandwagon. It gave birth to monstrosities like RxJs - which some people actually use, and I don't understand how or why. Same for me with React - class based components are a lot less magical than all the useEffect and use* stuff. They're easy to reason about, and self-contained. I never really understood the drive for "pure functional components". There's so much cruft and artifacts that arise from that, it interferes with application feature deliver and performance. You end up spending your days doing crazy Redux or RxJs like things, increase complexity by an order of magnitude, all for very limited actual benefit (like theoretical time rewinding during debugging - which I have never actually had a need for).