java - Exception to the Law of Leaky Abstractions -

I have given a logic with the friendly encoder, which was lightly damaged by Joel from any new framework / toolbox It is very difficult to understand how to use it. I am trying to present a point, as long as "instability will be fine until they allow level of access to a lower level level". Example:

• Google's great Java-to-JavaScript compiler, has JSNI - the ability to write "native" JavaScript if you really want to.
• Being in Hibernate - The API is in SQLQ - the way to write the original SQL.
• Java - JNI - if you miss.

Is this sound? Am I missing something?

Thank you

The article was not that the intangible were bad, but to understand it What is under the hood, so that you can create an account for "unexpected" behavior and avoid them.

What happens in your friend program? machine language? :)