That’s a choice, I guess. I tend to do that too every now and then. I would not say that Chrome dev tools have no value though, as that’s where I get most of my debugging done.
Another aspect is the cycle, if you change your shader to see what happens, then compile, run, see the result, process it, modify your mental state, make another change etc. Formal set of debugging tools cuts out the “change, compile, run” part for the most part making the whole process a lot faster. But that’s me trying to sell you on the idea of a debugger at this point
That looks pretty cool, personally I see 2 issues with the current renderer:
- API largely non-existent. You can throw a thing at it to render, but that’s about it.
- No deferred shading (please don’t try to point out demos, I’m aware of those, I mean production-ready stuff)
I think if you’re not addressing at least one of those - it’s an exercise in learning more than creation of something that’s largely different from what already exists. That’s my point of view though. My biggest pains with the library as it stands.