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:
Object oriented programming rose to popularity a few decades ago, along with a great deal of indoctrination and marketing for both the paradigm and related products. It was pushed so hard and so widely that more than a few folks grew into their developer roles assuming it was the best approach to every problem. Of course, it isn't.
(It definitely is useful at times, though, so please don't condemn it just because it's sometimes a square peg in a round hole.)
I'm glad to see you have discovered an alternative, and I hope you will continue to expand your toolbox and aim for simplicity.
People don't realize that OOP was pushed because some companies, like Sun microsystems, profited from its popularity.
Can you give an example of when oop is preferred to functional?
When it's easier to think about a system in terms of objects. The classic example is video game Entities/Game Objects. GUI stuff has also been very pleasant with OOP as buttons and the like are all easily conceptualized and worked with when seen as objects.
ECS is arguably a better for game dev, so even that point is debatable.
I think desktop GUI toolkits are a pretty good use case for object-oriented design, mainly because mapping window/widget families onto class hierarchies is straightforward.
That's not to say that a good functional design is impossible; it's just not particularly obvious.
One of the best use cases is implementing abstract data types and hiding the memory management and other potentially unsafe optimization tricks behind a clean and high level abstraction.
Also since it's a logical/mathematical construct and not attempting to model the real world (like business logic), it's one case where inheritance hierarchies will remain stable.
Wasn't there a video a while back of a presentation that OOP was created as a joke or something, and the person was surprised people were taking it seriously. Might have been advertised as the creator or OOP.
I took the video as a joke anyways, not a serious thing, but who knows. I don't even remember if it was OOP, or some other paradigm, or language, or who knows what else.
If anyone could find/link to it, I'd love to watch it again, but I'm having no luck; so my memory may be faulty.