I posted this because, frankly, I was pretty amazed that someone managed to reproduce these features in Python and lose almost none of the ergonomics of Haskell

I posted this because, frankly, I was pretty amazed that someone managed to reproduce these features in Python and lose almost none of the ergonomics of Haskell. So from a purely academic perspective, I think this is a very impressive feat. Having said that, whenever I consider using something like this - language features of language A ported to language B - I always conclude that it doesn't make sense. If I want those features, I might as well just use language A. Trying to shoehorn them into language B is just going to make it difficult for newcomers to the codebase. That's not even mentioning the fact that these libraries inevitably have "blind spots" in terms of what's been (re)implemented. I'll probably realise hours or days in that that one language feature I need to implement something doesn't work correctly and now I've got to write some ugly workaround (which defeats the point of using the library for cleaner code), or scrap the work I've done and return to using vanilla language B.