ocaml-webmachine
lwt
Our great sponsors
- InfluxDB - Collect and Analyze Billions of Data Points in Real Time
- Onboard AI - Learn any GitHub repo in 59 seconds
- SaaSHub - Software Alternatives and Reviews
| ocaml-webmachine | lwt | |
|---|---|---|
| 1 | 5 | |
| 223 | 660 | |
| 0.0% | 0.8% | |
| 0.0 | 0.0 | |
| about 2 years ago | about 2 months ago | |
| OCaml | OCaml | |
| GNU General Public License v3.0 or later | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
ocaml-webmachine
-
Ocaml for web development
We (a small company creating specialized inventory management and e-commerce systems) use Dream for web development. Webmachine and Cohttp for creating RESTful APIs. HTTP-clients with Ocurl and Cohttp. We are very happy with our choice of technologies.
lwt
- Por que aprender OCaml?
-
Ocaml for web development
Here is link number 1 - Previous text "Lwt"
I do only very basic web development but have been generally happy with it. One problem I hit was that mssql only works with one of OCaml's async libraries (Async) whereas multipart forms only works with the other, incompatible, async library (Lwt).
-
From TypeScript to ReScript
I have to admit I don't know much about ReScript and only have very basic exposure to OCAML, here is how you do await in it:
https://github.com/ocsigen/lwt
The `let* in` is a generic syntax for monads, it doesn't need a special one just for promise. This was in fact a debate back when async/await was in consideration for ECMAScript, but special syntax is hip so now we have `async/await` for Promise, `.?` for optionals and `flatMap` for arrays, basically the same thing.
-
Dream – Tidy Web Framework for OCaml and ReasonML
Dream doesn't have much of a system call dependency footprint itself. It's basically just a convention for plugging request -> response functions into a web server. Some of its native dependencies will have to be replaced by Node equivalents. Soon after that, it would be portable to Node.
There is already work underway to port Dream to Mirage, to run in unikernels: https://github.com/aantron/dream/pull/22
Lwt, Dream's promise library, is itself getting ported to run on top of libuv: https://github.com/ocsigen/lwt/issues/813
libuv is, of course, the I/O library that powers Node, so it might be practical to run Dream as a native node module very soon after doing this.
(As an aside, I'm supposed to work on that libuv project, but instead I've been working on Dream :P)
What are some alternatives?
async - Jane Street Capital's asynchronous execution library
dream - Tidy, feature-complete Web framework
sihl - A modular functional web framework
ocurl - OCaml bindings to libcurl
ocaml-cohttp - An OCaml library for HTTP clients and servers using Lwt or Async
genType - Auto generation of idiomatic bindings between Reason and JavaScript: either vanilla or typed with TypeScript/FlowType.
soupault - Static website generator based on HTML element tree rewriting
rescript-compiler - The compiler for ReScript.
melange - A mixture of tooling combined to produce JavaScript from OCaml & Reason
Tomorrowland - Lightweight Promises for Swift & Obj-C
from-typescript-to-rescript - Frontend of https://Inhyped.com written in TypeScript and rewritten in ReScript