News for hackers. Stuff that matters.
Re:Weep for Graphics Programming by sillysaurus3 on Tuesday May 03, 2016 @09:42AM (#11620513)
The issue is that every driver implementation ever ships with a slightly different implementation of that complex parser. That means (every mobile device)X(every OS update) and (every PC ad-in card)X(every driver update) all have the potential to misinterpret/reject your shaders in slightly different ways.

This doesn't have anything to do with shaders as strings. It's been true since the beginning of shader programming, whether bytecode shaders or otherwise.

Re:Weep for Graphics Programming by ufo on Tuesday May 03, 2016 @09:55AM (#11620636)
His point is that shaders-as-strings have a larger surface area for misinterpretation than shaders-as-bytecode.