title: EGL vs GLES 2.0 on Android (e.g. Java)
body: <p>(experienced c programmer, pre-shader, fixed function open gl. competent Java programmer)</p>
  
  <p>I have been working with GLES on Android and have gotten the examples to run (both native and Java). In particular, the textured triangle example.  What is completely confusing me is the "relationship" of Khronos EGL and the android GLES interfaces.</p>
  
  <p>Are these parallel, independent interfaces (API)?
  Is EGL supposed to be a platform independent (neutral) interface?
  EGL appears to fully support GLES 1.0 and 1.1 but does not support ES 2.0 (on Android)?</p>
  
  <p>So, it appears to me that EGL is <strong>supposed</strong> to be a platform neutral, parallel interface, <strong>BUT</strong> it does not fully support <strong>GLES 2.0</strong> (on Android); So if you're writing GLES 2.0 code (on Android), you are better off just using the GLxxx API rather than the EGLxxx API (and having to resort to the GLxxx API anyway). As far as I can tell, you don't ><strong>HAVE</strong>&lt; to use EGL for anything since it only supports a subset of the ES 2.0 API.</p>
  
  <p>(Every example/book/reference either mixes the two, uses the native interface or uses only EGL 1.1 features; Am I missing something fundamental here?)</p>