Logging could be done in a round robin fashion where old logs are dropped so one always keeps the latest x logs in the database/cookie. One could also send thelog back to the server if needed.
That way we wouldn’t need alert calls. Especially forgotten alert calls that goes into production.
Create a way to run code on the server, code that users can upload. The server should still be safe from abuse.
Making things interactive is a different horse. For developing web applications we have to use binaries, byte code or script at the server. Since running code uses resources and can choke the server there are very few gratis solutions. We must pay to get an account which we then can use up to a certain Mbits of traffic and Mbytes of data and possibly Mseconds of processor use.
Why not extend this kind of reduced power scripting to the server? Limit processor time, RAM usage and HD space. I have been thinking about how to limit dotnet or java but come to the conclusion that since the environment isn’t built for it it will be a faulty solution to start with.
If we instead created a new language and environment we could tailor the functionality to the needs.
If then people could easy upload web applications we would get an explosion of ideas and solutions.