Change request: Replace the GLSL parser about astexplorer HOT 1 OPEN

Other than being the author, my other disclosure is my own personal interest in this is having a nice UI to debug my ASTs

Thanks for the disclosure 😆 That's still an unsolved problem to me: What should the criteria be for adding a parser to astexplorer? Popularity? Language? There are no official guidelines at the moment.
On one hand I don't want to add everybody's toy parser, on the other hand small projects an still be very useful to others.

In the long run it would be cool if it were possible to also dynamically load parsers from npm to provide some kind of "ad-hoc" playground (just like actual code playgrounds work I suppose). But a couple of other things need to happen first to make that work.

But coming back to your question, I don't see a problem to simple add your parser. We don't have to remove the other one yet, though of course we eventually should (or at least hide it) if it doesn't receive any updates anymore.

I suggest you have a look at existing parser integrations for how to add your parser!

from astexplorer.