Name: Anonymous 2014-05-15 12:33
A simple new web (HTTP, HTML, JS) replacement based on s-expressions and lisp. It would be useful for things like file hosting, wikipedia/wikis, BBSs, online newpapers/blogs, imageboards, youtube/mediagoblin style video sites.
Instead of XML we use s-exp for markup. It will be a very simple functional markup language that could be defined in a page or two. We will not allow it to grow and grow horribly like the W3C to the point that it's impossible to implement from scratch.
Instead of javascript we use a simple lisp language (similar to R5RS without continuations) which is interpreted with strict resource and permission bounds, so it will never do anything you do not allow it including swamping your computer down like current js JIT systems.
For servers, instead of tools similar to PHP we will use systems inspired by type-checking that are able to statically ensure that no vulnerabilities in the class of XSS/SQL injection/... exist.
1. A first draft design needs to be created.
2. It should be easy to get something up and running quite fast by writing a proxy that translates all this s-exp stuff into HTML - just for the purpose of prototyping.
3. Reference implementations from scratch - focus on low memory usage and stability (using safe languages instead of C or C++).
Instead of XML we use s-exp for markup. It will be a very simple functional markup language that could be defined in a page or two. We will not allow it to grow and grow horribly like the W3C to the point that it's impossible to implement from scratch.
Instead of javascript we use a simple lisp language (similar to R5RS without continuations) which is interpreted with strict resource and permission bounds, so it will never do anything you do not allow it including swamping your computer down like current js JIT systems.
For servers, instead of tools similar to PHP we will use systems inspired by type-checking that are able to statically ensure that no vulnerabilities in the class of XSS/SQL injection/... exist.
1. A first draft design needs to be created.
2. It should be easy to get something up and running quite fast by writing a proxy that translates all this s-exp stuff into HTML - just for the purpose of prototyping.
3. Reference implementations from scratch - focus on low memory usage and stability (using safe languages instead of C or C++).