thick bindings, was Re: Vulkan is here!

[tmoran@acm.org]

> p.s: I dont get it why people don't systematically make a thin binding,
> standalone, and then undertake any other Ada-ized layer over it
> separately. I hate extracting stuff from others "wool ball".

A thick binding, like any API, creates an abstraction intended to be
easier and safer to program than coding at a lower level.  If you don't
like the abstraction, don't use it - it's straightforward to code the
necessary lower level thin binding instead.

A thick binding makes many assumptions about the state of the machine and
coding at the thin binding level likely makes those invalid.  Luring the
programmer into trying to code at two different abstraction levels at
the same time is not a kindness.