I wouldn't be surprised if the media arm foisted this insanity on to the consumer electronics arm but it's all Sony as far as the end user is concerned. About the only ray of sanity in Sony was the PSP and PS3 which were pretty standards friendly and still are but even there it's not hard to see signs of interference. e.g. the PS3 has for the last 18 months or so enforced Cinavia audio watermarks which appear in some DVD and Blu Ray discs. Will it stop people ripping discs into media files? Of course not. Instead they'll just buy non-Sony kit to play it on. It's self defeating.
As for WebGL, I've voiced my own concern about WebGL, but since it's essentially OpenGL ES 2.0 with relatively minor differences I don't it's particularly relevant to the point I was making.
I agree OpenGL ES 2.0 could do with some proper client side code for matrix calculations and so on. It's very frustrating to program in JOGL, or libgdx or Android and realise they all implement essentially the same stuff (e.g. they all have a column first matrix class) but in entirely different ways
Just because a high level representation of a shape is decomposed into something else does not mean it's convenient to force an app through the lowest level. Forcing an app to decompose a mesh, quad or a poly into a fan, strip or individual triangles, including coping with all the degenerate cases is a needless development burden.
OpenGL ES 2.0 is meant for embedded devices where such a restriction might be a reasonable compromise. It isn't a reasonable compromise in a desktop where the GPU or the driver could do it far more reliably, efficiently and accurately than some random app.
"Mr. Watson, come here, I want you." -- Alexander Graham Bell