Thanks for the feedback. The clauses in statements are not order dependent, so they can be specified in any order. No need to remember what goes where, just splatter your thoughts out.
Vely is meant to be more human-readable than APIs; it leans more declarative than API. Each statement typically does what a number of C API calls would do, so the idea is to save time by saying what you need done rather than placing a number of API calls. At the same time, it's safer because it handles all the details and has a memory garbage collector.
For instance, web-call does all kinds of GET and POST calls. run-query does SQL queries. write-string composes complex strings. Etc.
Vely is also a thin framework. You can fire up FastCGI application server in minutes, and use the same program to run a command-line program.
Vely is meant to be more human-readable than APIs; it leans more declarative than API. Each statement typically does what a number of C API calls would do, so the idea is to save time by saying what you need done rather than placing a number of API calls. At the same time, it's safer because it handles all the details and has a memory garbage collector.
For instance, web-call does all kinds of GET and POST calls. run-query does SQL queries. write-string composes complex strings. Etc.
Vely is also a thin framework. You can fire up FastCGI application server in minutes, and use the same program to run a command-line program.