This project was interesting. Recently, I've been digging into the functional programming paradigm. This is one of my first tries at it. I've been doing OOP until recently, but this project really was impressive to me. The whole implementation took about nine hours. Functional programming is much less convoluted. I spent more time programming than deciding on a good name for a certain identifier.
Not only is functional programming more efficient, but I can also see that it's much less tedious to write automated tests for. I only have to take care of the local scope of the function I am writing a test for; there is no need to deal with the parent's inherited mess or even any parent's mere state. I just have to write the test for the function.
I have scraped the Cambridge Dictionary to collect the data.
The project is licensed under MIT at:
If your OO experience is from Java, the problem is with Java culture, not OO in general.
Putting functions and properties into classes is good and helpful. Whyever the fuck Java people want to implement the factory pattern three times in every application they make is convoluted and asinine.
My OOP experience isn't from Java, but I get your point. I don't really have a dislike for OO; it sure does have its applications. I once met a dude who was trying to use an object oriented library in a functional way; the result of that was a mess full of complications. I feel a good balance is necessary.