As a comparison would be to say - what if it was actually quicker when implemented in the DOM or Canvas ?
Would it then make sense to call it TraceDOM or TraceCanvas ?
If the killer / primary feature of the product is speed then it should really be TraceFast / TraceSpeed / TraceMegaSuperQuick (ok, not great names but you get the idea).
Comments
The name seems like a bit of a misnomer, I only just now realized this wasn't a WebGL debugger.
Yeah I agree.
The GL part is just an implementation detail.
As a comparison would be to say - what if it was actually quicker when implemented in the DOM or Canvas ?
Would it then make sense to call it TraceDOM or TraceCanvas ?
If the killer / primary feature of the product is speed then it should really be TraceFast / TraceSpeed / TraceMegaSuperQuick (ok, not great names but you get the idea).
Its a GL javascript tracer :) plus there is the domain.
The name also confused me and I thought it would just be for tracing WebGL.
From a developer standpoint it's cool that it's in WebGL. As a developer-user I don't care, it just works well and fast!
I would genuinely suggest de-emphasizing the WebGL except in a behind-the-scenes way.
(I've bought and played with it, and can't wait to chase down a bug!)