Most of the times the suggested keywords are ok, but sometimes they are driving me away from the original intention

[pbiggar]

A user says:

It was difficult for me in the very first hour of adoption to have a clear understanding of the language syntax when using the editor and browsing the documentation: in the documentation before introducing the type system and other features, it would be great to have an overview of the overall syntax. In the "Getting Started" section it's not very clear what the different components do (HTTP API, REPL, workers... ) and how they can be glued together; maybe you could add a link to the Concepts section where the components are described in detail and enrich the Concepts section with more examples.

In the editor the most difficult thing for me is trying to correlate the auto-completed syntax with the intention of what I'd like to build, especially if some branching is required: most of the times the suggested keywords are ok, but sometimes they are driving me away from the original intention. A good thing is that it's very easy to access the variables and the built-in functions and the documentation is right there on top.

I literally love how the datastore part works at a functional level: very easy to setup and use! Didn't have time to test performance or scalability of it but super good UX. Do you have any data regarding the latency of database times?

Some more questions that arose:

• is it possible to reach milli/micro/nanosecond resolution in Date?
• do you have a link to the doc on how to parse parts of the URL (I found some example using the /uri/:field notation to have field as a variable but could not make it work)
• any way other than cookie/basic auth to secure an HTTP endpoint?