GL at about 1.2 feature set used to be actually solid, actually supported everywhere, and actually portable, and now it's not anymore,. That sucks, because it was basically the Python of the graphics world, and "*grump* here's how you build your own Python" is not a good answer.
-
If you take it to its logical conclusion, it is an argument to not deprecate any API ever because someone will have to re-write some code. There is an opportunity cost to maintaining APIs that are no longer the best or even good choices. There has to be a balance between these 2.
Right, that was me. To add a bit more context, it was about the fact that usage flags were added to textures (in iOS 9/El Capitan), and the default usage didn't permit writing or use as a render target. Matter of opinion as to whether that's a breaking change.
-
-
There were also some slight changes in shader compiler strictness around which types were permitted as attributes (no packed vectors, IIRC). Minorly inconveniencing code rot, IMO.
-
It seems to me a more strict checks more so than breaking backward compatibility. I guess it is a matter of opinion.
- 1 more reply
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.