One can live without it on a smaller scale. But for anything that will have any lifetime whatsoever it's absolutely essential. Distinguishing between a module's intended interface and its implementation details is what makes it possible to amend the implementation should the need arise. Without proper encapsulation every change must be assumed to be a breaking change, software maintenance costs go through the roof, module interactions become unpredictable, and that upstart kid who wears Chucks to work but knows how to write testable code eats your Wheaties.
Languages like Haskell rely on it as heavily as any other well-crafted system. Imagine Data.HashTable it were originally implemented using linear probing, and someone wanted to modify (upgrade?) it to use cuckoo hashing or hopscotch hashing instead. It wouldn't be possible to do without breaking existing software if users were permitted to directly access the underlying data structures.
You want encapsulate. Encapsulation. Encapsulating.
The "en" prefix means put into or on something. You're saying you're putting something into a capsule or "isolating it".
The "in" prefix in English usually is the negative, or "not".
Intolerable: not tolerable.
I figured, I'm a native English speaker learning Russian, as it happens.
Будем здоровы