The Go Programming Language (11)

4 Name: #!/usr/bin/anonymous : 2009-11-15 15:27 ID:TEbWqc1c

I agree, there's enough of C to go around multiple times.

If I wanted to make up a language nobody cared about, I'd make a language actually designed for generating and processing webpages (or XML) (ie not java, ruby or perl), the idea being that each page or form would be entirely contained within a file: the code for generating the form and the code for processing it. Each page would be standalone and stateless, allowing it to work with or without an "application server". (Using one would reduce execution/fork overhead, db connections etc. Without one you'd use mod_uselesslanguage, or a CGI executable)

For HTML, variables expected to be received would be declared, along with an optional source of the variable (ie "cookie", "post") and an optional function for validating that variable. The body of the program file would effectively be a gigantic select statement, eg "here is the part to use when someone GETs the form, here is the part to use when someone POSTs the form" and so on (PUT, DELETE, etc).

In SOAP/XMLRPC mode, the file would contain functions (marked public or private), each of which would declare a DTD for incoming data. A WSDL could be generated automatically from the list of public functions (eg returned on GET).

This thread has been closed. You cannot post in this thread any longer.