lwt VS dream

Compare lwt vs dream and see what are their differences.

dream

Tidy, feature-complete Web framework (by aantron)
Our great sponsors
  • Scout APM - Truly a developer’s best friend
  • Zigi - The context switching struggle is real
  • InfluxDB - Build time-series-based applications quickly and at scale.
  • SonarLint - Clean code begins in your IDE with SonarLint
lwt dream
4 8
602 997
2.0% -
8.4 8.0
25 days ago 28 days ago
OCaml OCaml
MIT License MIT License
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
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

Posts with mentions or reviews of lwt. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2022-02-13.
  • Ocaml for web development
    8 projects | reddit.com/r/ocaml | 13 Feb 2022
    Here is link number 1 - Previous text "Lwt"
    8 projects | reddit.com/r/ocaml | 13 Feb 2022
    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
    12 projects | news.ycombinator.com | 12 Jan 2022
    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
    10 projects | news.ycombinator.com | 9 Apr 2021
    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)

dream

Posts with mentions or reviews of dream. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2022-08-16.
  • Functional Reactive Programming
    9 projects | news.ycombinator.com | 16 Aug 2022
    > you might want to check out OCaml for general purpose programming

    Any tips on backend frameworks to look at? I need to write a small websocket service for a side-project and have always wanted to try OCaml. I came across https://github.com/aantron/dream.

  • so people are making these
    3 projects | reddit.com/r/ProgrammerHumor | 31 Jul 2022
    The framework I played around with for OCaml was called Dream: https://github.com/aantron/dream. I think it had built-in support for auth, but I didn't use it in what I was doing. I also barely scratched the surface of what it supported. On the whole, it seemed really nice though. The biggest issues I had were figuring out OCaml since I'd literally never used it before and figuring out how to make an HTTP call from within OCaml since the documentation can be iffy. Thankfully, Dream's documentation was actually reasonably good.
  • The New OCaml Website
    6 projects | news.ycombinator.com | 29 Apr 2022
  • Dream – Tidy Web Framework for OCaml and ReasonML
    10 projects | news.ycombinator.com | 9 Apr 2021
    AFAICT all of these are client-side frameworks. Dream is a server-side framework. I currently write my server with Dream and use regular JS React on the client.

    If you glance at most of Dream's examples that serve an interactive client, you will see that they serve JavaScript:

    https://github.com/aantron/dream/tree/master/example/k-webso...

    You can use anything you want for the client, and I use the JS ecosystem heavily in my own usage.

    There are several full-stack OCaml examples, but that's entirely optional:

    https://github.com/aantron/dream/tree/master/example#full-st...

    As for server-side comparisons, OCaml is much easier for me to work with than, for example, TypeScript for many reasons. The first is that I can compile several hundred OCaml files, in the rare case of a full rebuild, in less time than running tsc incrementally on a small project, resulting in a much better iteration experience.

    10 projects | news.ycombinator.com | 9 Apr 2021
    ...and just to make it slightly more confusing, ReScript changed the ReasonML language somewhat, prompting another fork, Melange, which sticks with ReasonML.

    In any case, Dream has examples showing full-stack (OCaml client+server) usage with both ReScript and Melange:

    - ReScript: https://github.com/aantron/dream/tree/master/example/w-fulls...

    - Melange: https://github.com/aantron/dream/tree/master/example/r-fulls...

    For good measure, there is also an example with the other OCaml-to-JS compiler...

    - Js_of_ocaml: https://github.com/aantron/dream/tree/master/example/w-fulls...

    10 projects | news.ycombinator.com | 9 Apr 2021
    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)

    10 projects | news.ycombinator.com | 9 Apr 2021
    That page doesn’t link to the examples in GitHub whose README [1] is unexpectedly informative.

    Anyone using this in anger?

    [1] https://github.com/aantron/dream/tree/master/example#readme

    10 projects | news.ycombinator.com | 9 Apr 2021
    Yes. OCaml + all of the 3 OCaml-to-JS compilers support OCaml syntax.

    Dream itself demonstrates:

    - Server and client both written in Reason, using ocamlc+Melange https://github.com/aantron/dream/tree/master/example/r-fulls...

    That example could also have been written in OCaml syntax, because ocamlc (native) and Melange (JS) both support OCaml. However, Reason is nicer if you want to use React with JSX.

    - Server and client both written in OCaml, using ocamlc+Js_of_ocaml https://github.com/aantron/dream/tree/master/example/w-fulls...

    The remaining example uses Ocaml on the server and ReScript on the client, using the ReScript compiler. However, you could use OCaml on the client with the ReScript compiler. Just as with Melange, you would lose access to nice JSX syntax https://github.com/aantron/dream/tree/master/example/r-fulls...

    It's definitely a lot and not user-friendly to have to decide between all these options, but the community is experimenting greatly right now... so it's good and bad, and that's how it is :/

    As for Node.js, using ReScript syntax requires you to use Node.js on the native side, but that is the only coupling. If you write your native side in OCaml or Reason, you can compile it to native code with ocamlc (technically, ocamlopt is the internal command; nobody uses either one directly, but the build system calls them).

What are some alternatives?

When comparing lwt and dream you can also consider the following projects:

sihl - A modular functional web framework

rescript-compiler - The compiler for ReScript.

opium - Sinatra like web toolkit for OCaml

async - Jane Street Capital's asynchronous execution library

ocaml-webmachine - A REST toolkit for OCaml

ocurl - OCaml bindings to libcurl

re-web - Experimental web framework for ReasonML & OCaml

ocaml-cohttp - An OCaml library for HTTP clients and servers using Lwt or Async

jsoo-react - js_of_ocaml bindings for ReactJS. Based on ReasonReact.

genType - Auto generation of idiomatic bindings between Reason and JavaScript: either vanilla or typed with TypeScript/FlowType.

httpaf - A high performance, memory efficient, and scalable web server written in OCaml