What to read about OOP js before the gang of four?

Question

JavaScript

I open a gang of four, I see:

Before reading the book, you understand how "interface inheritance" differs from "implementation inheritance"

.

Then I realize that I don't know what it is. Worked with JS and Python.

Question - what to read before the gang of four to consolidate OOP in the context of JS? (or at least in a Python context). To understand what an interface is, interface inheritance and implementation inheritance, and so on.

I opened Bucha, but it’s just as dry as possible for me (in most cases, it’s a good sign that either I didn’t grow up to this book, or the book doesn’t fit. The beginning of the gang of four was interesting.)

Answer 1

The Gang of Four is not about OOP, but about OOP-based design patterns. It makes sense to study patterns rather than in the context of JS, but in the context of then TypeScript. It provides DI implementations, interfaces, decorators, and IoC containers. In js, all this is implemented in a very special way, and even without typing, this is not very efficient IMHO.
And about OOP, read on the Internet simply, the main thing is to understand the basic principle: OOP gives you the opportunity to organize data and methods for working with this data within a single entity. Well, the consequences arising from this: encapsulation, polymorphism, inheritance.

Answer 2

https://refactoring.guru/files/design-patterns-en-...
https://refactoring.guru/en/design-patterns/book

Answer 3

Matt Zandstra

Answer 4

JS is not the best language for learning OOP.
Learn in php, there is everything you need to master OOP.

Answer 5

1. Well, just do if the iron allows, then it will work faster in parallel.
solid-state drives in multiple threads allow you to read data faster.
2. The built-in mechanisms of the database work, as a rule, work faster than compiling this logic yourself, Mongo allows you to store "reference" data (which, when requested, are loaded from other tables themselves).
3. The advantage of Mongi is that you can simply shove all the answers into the collection. For example, you have one database with some data, and another database with this data but already organized according to a different principle, in which, for example, all answers, all relationships, etc. are located, try to implement another database, with pre-prepared aggregations of all the necessary data .