Good question! The main reason is that sqlglot is written in Python, so it wouldn't integrate natively with our Go codebase. We actually faced a similar decision with pg_query_go (https://github.com/pganalyze/pg_query_go) and passed on that too, anything that requires bridging another language means translating the AST back into Go, which adds a performance cost we wanted to avoid.

I wrote it, but of course I used AI to polish it :smile: It would actually be ironic if I didn't use Claude to write about how Claude accelerated my engineering!