Why won't browsers build in the OpenGL specification?

Question

Browsers

Have there been previous attempts to run OpenGL in a browser frame window, and not try to "iron" the sluggish WebGL, why did they start creating WebGL, because of license problems or for technical reasons?

Answer 1

there are many reasons why everything is the way it is now:
-languages ​​like c\c++ make it too difficult to develop on the web and the entry threshold becomes too expensive
-a huge number of security problems
form -development time becomes incomparably longer
-a huge problem arises in principles due to almost direct working with hardware, different architectures, different hardware, different operating systems, different versions of libraries, etc.
-jit for such languages ​​is almost impossible to do due to the compilation time and the fundamentals of the languages ​​themselves, in addition, the speed of the final code is good if it is on the level of what is now - there are still
a ton of reasons why js and other scripting languages ​​​​dominate
If you don’t feed bread but let the native, then maybe it’s not necessary on the web, but if it’s still on fire, then smoke ppapi \ npapi \ chrome-native, etc.