Why is the definition of encapsulation wrong?

Question

OOP

The purpose of encapsulation is to group objects together, not to hide information, but many people still believe that encapsulation is about hiding, where did it even come from?

Answer 1

The purpose of encapsulation is the union of objects

who told you that?
The word encapsulation itself comes from the Latin "in capsula", which can be translated as "closed in a box".
The purpose of encapsulation is to hide complexity. Not information, not data, not code, but complexity.
Imagine you have a light bulb with a switch. You can simply press the switch to turn it on or off. You don't need to understand the electrical circuits inside this device to have light. You just need to use a simple interface - a switch. This is what encapsulation is. The interior of a light bulb with a switch is encapsulated from you.

Answer 2

There is enough structure to combine objects, even OOP is not required.
In capsula - "in a box". Mandatory for normal architecture separation of internal data from external interfaces.
Of course, it also has nothing to do with "hiding information".
Read normal textbooks and do not listen to the nonsense that dropouts mumble into the cell.

Answer 3

Good question to ask you. Why did you give it wrong?)))
Well, come on answer;)

Answer 4

Who knows, maybe from Wikipedia?
Access modifiers had to be included somewhere, so they stuffed them into encapsulation. Do not shove them into inheritance and polymorphism.