Thanks! I really like your client side SDK approach, giving users the ability to use their own IDE / tools is always a plus. (+ building a web IDE is a pain haha)
The no-code approach taken by these automation apps (Make, Zapier..) makes them super accessible, but i agree, when any kind of business logic is involved nothing beats a few lines of code.
You could setup a Chunk as only one "step" of a Make/Zapier workflow. Giving you code-control only where you need it.
We could probably make that even easier by building integration for Make and Zapier.
Glitch is definitely the closest in terms of usage. We in fact used Glitch ourselves quite a lot. But even running the simplest piece of code on Glitch still requires you to write all the boilerplate code (e.g. setting up a node express HTTP server).
And of course, Glitch stops every instances after 5min of inactivity and it takes a solid 30sec to wake them up after.
Glitch is unbeatable in the frontend part. But we want to make the backend dev experience more seamless.