Abstraction - the means of hiding the details. The Webster definition:

Quote

For us programmers, it has a special significance. Anyone who has worked on a large or complex program understands the need for this concept. Encapsulation and information hiding are extensions of this fundamental concept. It helps the programmer(s) handle the problem as effectively as possible. But the question arises: how much is too much? Some would argue never, as it helps regardless of the amount/level. However, I think there comes a point where abstraction takes away functionality, so a balance must be struck. Otherwise, the programmer may be metaphorically coddled, but his/her ability to solve the problem at hand may be severely limited.

No matter what side of the "fence" you're on, at least understand your viewpoint and remain convicted. There is nothing worse then a hypocritical flip flopper. Arguing the effectiveness of an abstract high level language by way of condemning low level abilities and then turning around and saying everything is the same at a basic level makes no sense. Why? Either low level concepts are good or they are not. One of the most beautiful aspects of programming/software development is the lack of tepid/lukewarm/on the fence views on items. Either it is or it is not. It is 1 or 0, on or off. The binary concept makes such a good analogy, no wonder computer systems are built on it.