lwt
sihl
| lwt | sihl | |
|---|---|---|
| 6 | 1 | |
| 704 | 357 | |
| 0.7% | 0.0% | |
| 7.4 | 4.3 | |
| about 2 months ago | 4 months ago | |
| OCaml | OCaml | |
| MIT License | 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.
lwt
-
Go is my hammer, and everything is a nail
> Also, didn't OCaml have weak support for concurrency? Has that changed recently?
OCaml has had Lwt for concurrent IO for long enough that it is now being deprecated in favor of Eio[1]:
https://github.com/ocsigen/lwt
[1] https://github.com/ocaml-multicore/eio
- Por que aprender OCaml?
-
Ocaml for web development
Here is link number 1 - Previous text "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)
sihl
-
Dream – Tidy Web Framework for OCaml and ReasonML
Really exciting to watch the developments in OCaml/Reason web frameworks/libraries. I love the language and wish I could use it instead of Ruby for my personal projects at least. Others that have caught my interest are:
Sihl: https://github.com/oxidizing/sihl
ReWeb: https://github.com/yawaramin/re-web/
Of course, if you're interested in OCaml/Reason and don't know about Revery you're missing out.
What are some alternatives?
async - Jane Street Capital's asynchronous execution library
dream - Tidy, feature-complete Web framework
ocaml-containers - A lightweight, modular standard library extension, string library, and interfaces to various libraries (unix, threads, etc.) BSD license.
ocurl - OCaml bindings to libcurl
patoline - Patoline typesetting system
ocaml-cohttp - An OCaml library for HTTP clients and servers using Lwt or Async
ocaml4noobs - Tutorial de OCaml para iniciantes na Linguagem.
genType - Auto generation of idiomatic bindings between Reason and JavaScript: either vanilla or typed with TypeScript/FlowType.
eliom - Multi-tier framework for programming web and mobile applications in OCaml.
melange - A mixture of tooling combined to produce JavaScript from OCaml & Reason
opium - Sinatra like web toolkit for OCaml