13:16 youngfaceatold: The worst case is when context switch is needed, but it's not that bad even software context can be accelerated, I need to look but it much seems that egl allows to maintain two contexts, so you never switch expensively, but display lists would allow it too.
13:34 youngfaceatold: I do not think there's any problem with EGL I remember there was context sharing, so state can be shared, you can share as to what you want, hence making the context current is cheap by default, but some surfaces can take memory address anyways, in which case you just flip the pointer to already compiled context
16:36 youngfaceatold: There in gl theory it is not about context, but rather object
16:37 youngfaceatold: And objects are split to two
16:37 youngfaceatold: Immutable and mutable
16:38 youngfaceatold: Immutable context representatives can inherit ctx parameter
16:57 youngfaceatold: Me, very smart man
17:01 youngfaceatold: In some way it's understandable
17:01 youngfaceatold: You create a bunch of contexts that have different objects
17:02 youngfaceatold: Objects which are shareable or not, and you can just name the object
17:02 youngfaceatold: State tracker gets the context
17:20 youngfaceatold: Arguably very complex scheme whereas two objects of context names are made accessible concurrently by one thread
17:21 youngfaceatold: So both are copied the state for inside the driver