abstractions

In Haskell there are a lot of abstractions, the compiler is also very aggressive, but I don't know the details.

Absolute beginners are confused by polymorphism and loop constructs because they don't understand the problems the abstractions solve.

And an interpreter is always a pile of convoluted mess, leaking multiple abstractions in between layers (if you're lucky enough to even get any distinct layers at all).

With the C++ code, you typically have to spend more time removing abstractions before you can start actually tuning it.

It involves breaking down problems, creating abstractions for those problems, and turning them into code.

In the spirit of extensible web manifesto, it's a low-level primitive for JS libraries to build convenient higher-level abstractions on top of.

We now have a number of different ways of articulating abstractions in source code.

And Python, with all its magic methods and abstractions, made that very hard.

I found the abstractions Seaside provides (continuations and components) to be much more powerful than what the other frameworks gave me.

Marathon doesn't have the service, secrets, or pod abstractions, for example.

API leaks abstractions and does not provide any domain-specific semantics.

Counter-intuitively, suddenly everyone has become a devops luddite when it comes to a genuinely novel approach even though container abstractions have already proven themselves at scale.

For you (and me, for that matter) understanding the meaning of the abstractions first helps you learn the "less important" specifics of operations on them and how to apply them to new areas.

"Simple and predictable to use" is subjective, but generally lends itself well to systems built around exploiting a few Grand Abstractions to compose higher functionality.

Abstractions so that you code doesn't have to worry about different os-es, cloud providers, etc.