MicrosoftThis is actually a very valuable direction.
What many people miss is that Classic ASP wasn’t popular because of VBScript itself, but because it dramatically lowered the friction between HTML, HTTP, and the database. You could think in pages, not architectures.
Replacing ActiveScript with nothing was one of Microsoft’s biggest strategic mistakes. Not every problem needs microservices, ORMs, containers, or a full framework stack. Sometimes people just want to write a small application fast, with minimal cognitive overhead.
History already proved this point. When Classic ASP stagnated, PHP did not win because it was beautiful or elegant. It won because it preserved the same low friction mental model. That is why it dominated such a large portion of the web.
A modern, cross platform, ASP like engine on Go or Lua, something like page.gasp, page.lasp or page.asp, even with a VBScript inspired syntax, would absolutely attract users. Especially for intranet tools, admin panels, internal ERPs, and small but real applications.
The key is not to recreate ActiveScript itself, but to preserve the ASP spirit: HTML first, simple request and response handling, and low mental overhead.
Thank you for your efforts. I have added this project to my watchlist and will test it.
Mental overhead? you are assuming VBscript is so simple that it does not require thought. It is simple to make a solution yes, but the complexities it solves is outstanding. Why waste time, with full frameworks and containers, etc? one language, one solution, one developer. but containerization I will add to my list. Also when are they going to opensource it?
