And dependency injection!
Every class needs to use DI for calling other classes, even though we’ll have anyway just a single implementation for all of them, and we won’t be using this flexibility at all (not even for tests where it might be useful for mocking dependencies).
Oh wow I was not aware of the drama behind Bazzite.
Years ago I installed manjaro and I want to rebuild the system soon, I use that computer for gaming so Bazzite seemed the most suited to that, but when I tried it in a VM it gave me the feeling of being unpolished compared to Kinoite (the documentation of how to use fedora silverblue is excellent, and bazzite deviates quite a bit from that and adds a lot of custom tools and utilities).
I think I’ll go with Kinoite after reading this, hoping that it works relatively well on nvidia…
It might be nice to use in some very specific cases (e.g. addition-operation is a binary-operation AST node which is an AST node).
In most of the cases it just creates noise though, and you can usually do something different anyway to implement the same feature. For example in rust, just use enums and list all the possible cases and it’s even nicer to use than inheritance.