You can learn F# with dotnet core, which has a better ecosystem for web development. OCaml is quite poor in that domain.
https://github.com/fable-compiler/Fable/blob/master/README.m...
There's a newer branch called Fable Arch which I believe is focused on promoting the Elm Architecture for structuring web apps:
https://github.com/fable-compiler/fable-arch
FunScript is another alternative:
There are several active projects and bindings that you can take a look at there: https://github.com/fable-compiler
"Database access from a Suave.IO app isn't any different from database access from any other .NET / F# app you write."
Any way you like, really.
But removing delimiters in my opinion does not help readability. Most time is spent reading, not writing. It's similar to claiming more efficiency by removing lanes and signaling from a highway...
Then, whitespace has more meaning than it should in CoffeeScript, and inconsistent indentation is possible, whereas in Python/Ruby it is not without an error. Therefore a formatter can break your code.
Snippets/templates/autocompletion can save the work of typing delimiters. Delimiters can be enforced with CoffeeLint, but then that's optional, it is more work, and it is a friction point with people that do not see value in formatting.
CoffeeScript does not have a lot of tooling around it, and the community has moved on.
There are documentation tools like docco and codo, but there is no tooling that makes it as well integrated with the language as JavaScript + JSDoc, where there is tooling that can verify types, function parameters and return types giving you a lot of static analysis power.
Then, the entire point of a scripting language is not having to compile. With CoffeeScript you lose that advantage to some extent, and the compiler does not filter many errors, making it a bad tradeoff.
I've been using Coffeescript in projects for about two years. I know people have raised issues with it vs ES6, but I still really like Coffeescript. I feels more natural with my Scala/Ruby background and it outputs into Javascript in ways that (mostly) make sense and are predictable.