Definitely get that. Being hammered by scrapers is a massive PITA (especially with latest aggressive AI crawlers). We focus primarily on allowing people to automate their existing workflows. For all hosted workflows we have rate limits to prevent mass scraping/affecting server workload in any real capacity. In fact, because we don't load js/html and hit endpoints directly I would guess that we consume less server resources in the end.
The requests still route through your servers/the data still lives with you. Kampala is a powerful tool but I don't see people replacing the actual apps with it. Most of our customers use it for automating repetitive actions in legacy dashboards.
A vibe coded thought experiment, interesting but likely not worth the tokens to duplicate work.
I just skimmed the fully vibe coded page and saw the quote “Machines now speak every human language better than most humans.”. Interesting, and maybe possible if languages never change.
Your loop is wrong, as it will go ‘intent -> llm(?) -> result’. Which doesn’t need to compile, but the llm its own black box of magic function that may or may not reproduce the same result based on intent. Also I would think the number of tokens would be concerning, as your example prompt looks 3x larger then the code snippet.
May be a great compliment if someone does try, haha. But seriously, the real value isn't in the text since it is very specific to my firm and work experience, the value is the underlying design logic and the specific 'if-then' professional constrains baked into the system. Plus, the audit logs are part of a 'transparency' experiment, if it helps someone else build a better tool for the industry, Im all for it!
reply