let's create the future: a minimal lisp based web

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++).

>>58
Link at the bottom in case anybody forgot, but mostly because I just noticed the markup system I thought up over the last few days was essentially this one and I don't want anyone else to waste their time just because they didn't have their old /prog/ stuff sorted.

On a different note, how does the layouter know which text segments belong together? One obvious way is to tag sections in the original source and act on those in the layout, but that would basically recreate HTML, complete with its <div> madness you can see in just about any site. I propose the following: Sections that are to be layouted differently are put into different units, like files. Layout would still be pretty straightforward: After all, every unit already has a unique name and can be accessed without any trouble or relevant overhead. However, the important thing remains clean. No XML ENTERPRISE shit, not even ((excessive amounts) of (sexprs)). Just content and maybe simple lispy markup.

Also, what is the consensus on having an index for each site? Right now, there is no way to see which ``subpages'' are accessible. What if every site contained an index that lists all accessible items, complete with their associated units for content and layout? In theory, this sounds easy to navigate and provides a simple entry point for clients, but I might have missed something important.

_{http://cairnarvon.rotahall.org/2010/05/25/towards-a-better-bbcode}