I don't see how this is a scripting language and runtime; so, maybe I'm totally missing the boat and everything below is nonsense... I think DSLs like this tur

I don't see how this is a scripting language and runtime; so, maybe I'm totally missing the boat and everything below is nonsense... I think DSLs like this turn into one thing: maintenance nightmares. I love the idea of them, I've just _never_ seen one be useful for more than a demo. Especially, for something as complex as interacting with the browser... Why not just use a visual tool and record the session with something like selenium? At this point, the idea of a "DSL" for non-programmers is pretty much a fantastic myth. I think DSLs should really only be used when they enforce quality, not to have a nicer looking statement. Same rule applies with macros, and lmao, if they aren't responsible for most DSLs. I haven't even begun touch on the problems with errors, debugging, warnings, deprecating, updates, etc. which also come with a DSL. The SDK setup looks an awful lot like I'm just using selenium with node and this is on-top of that entire debugging nightmare, is there more to it than that and the DSL? As well I'm curious, how do you reliably use the web without selectors? I see it referenced, but I don't see "how," and that quite honestly seems like the coolest thing on the readme. Again, I love the idea, it looks slick. Just based on my experiences, it seems like how nightmares, not dreams, start...