dream
package.elm-lang.org
dream | package.elm-lang.org | |
---|---|---|
9 | 13 | |
1,524 | 296 | |
- | 0.0% | |
7.7 | 0.0 | |
18 days ago | about 1 year ago | |
OCaml | Haskell | |
MIT License | BSD 3-clause "New" or "Revised" 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.
dream
-
Ask HN: What Happened to Elm?
> It sounds like you read my statement as "run the exact same code in node or OCaml" which I agree would have been very hard.
Hello! Indeed, I did misunderstand you. I agree that it was possible to share some parts of the code between Reason's JS target with BuckleScript, and native target with the stock OCaml compiler. I think a pretty reasonable number of people did that. Actually, it's still possible to this day even with ReScript e.g. https://github.com/aantron/dream/tree/master/example/w-fulls...
> Between the breaking changes and the general change in development philosophy...switching to the ReScript compiler for my project would have required nearly a complete rewrite.
There were perhaps a couple of minor breaking changes but can you explain why it would have required a near complete rewrite? I wasn't aware of anything major like that. ReScript even supported and as far as I know, to this day continues to support the old Reason syntax.
-
Functional Reactive Programming
> 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
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
-
Dream – Tidy Web Framework for OCaml and ReasonML
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).
package.elm-lang.org
- Por que Elm é uma linguagem tão deliciosa?
-
Ask HN: What Happened to Elm?
Also the fact that their package manager is strongly coupled against https://package.elm-lang.org/. There is no way to override it. This means that if that package site ever goes down, you will be left with an unbuildable project. Seems pretty risky to me.
-
How do yall share Elm codez within your organization?
Imagine, for example, you have a component library that you don't want to publish to the public package.elm-lang.org. How do you make that available just within your company?
-
Advice on porting a package to 0.19.1
Not to be silly but I was getting ready to do my port & all but clicking on "source" from with package.elm-lang.org takes me to elm-charts, not elm-plot.
-
[Media] Why is namesquatting on Crates still not resolved after almost a decade? These crates have had absolutely no activity for years (2nd example in comments)
Elm has packages prefaced with the repo owner, so its mdgriffith/elm-ui and not just "elm-ui".
-
Entering periods into Float fields is difficult, what's the better way to do it?
If you're dealing with some kind of currency it's better to use a Decimal type which has few packages on the ecosystem.
-
Why is Elm documentation so poor?
If you are looking for a complete API documentation you should be browsing https://package.elm-lang.org/ ; I still find it lacking compared to other programming languages, but it's definitely more complete that the starting guide.
-
Should I compose elements?
There are two ways of structuring state. Record with each page's state in its own field OR a custom type with the variants containing the state for the page (this is what you see in elm-spa-example or package.elm-lang.org). The tabs you describe behave like the first approach.
-
React to Elm Migration Guide
Elm is a strongly typed functional language, compiler, package manager, and framework. You write in the Elm language, and it compiles to JavaScript for use in the browser. The Elm compiler has 2 basic modes of development, and production. It optionally has a REPL if you want to test some basic code. The package manager uses it’s own website and structure using elm.json, instead of package.json. The framework is what Elm is most known for, and was the inspiration for Redux.
-
Should I Upload The Binary Or Build The Code On
I was considering doing just that, using nginx server. I was using Evan's git repo for Elm packages (website: https://package.elm-lang.org/) (git: https://github.com/elm/package.elm-lang.org ) where he does uses that. So I think I will try this first and then consider deploying the binary if I can. Thanks for the advice!
What are some alternatives?
sihl - A modular functional web framework
proposal-pattern-matching - Pattern matching syntax for ECMAScript
rescript-compiler - The compiler for ReScript.
elm-format - elm-format formats Elm source code according to a standard set of rules based on the official Elm Style Guide
opium - Sinatra like web toolkit for OCaml
Elm - Compiler for Elm, a functional language for reliable webapps.
lwt - OCaml promises and concurrent I/O
elm-syntax - Library for generating Elm syntax from Haskell in a scope-safe way
ocaml-webmachine - A REST toolkit for OCaml
roc - A fast, friendly, functional language. Work in progress!
httpaf - A high performance, memory efficient, and scalable web server written in OCaml
guide.elm-lang.org - My book introducing you to Elm!