melange
vscode-ocaml-platform
melange | vscode-ocaml-platform | |
---|---|---|
15 | 4 | |
872 | 347 | |
2.3% | 0.9% | |
9.4 | 9.6 | |
3 days ago | 7 days ago | |
OCaml | OCaml | |
GNU General Public License v3.0 or later | ISC 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.
melange
- OCaml Syntax Sucks
-
Melange for React devs book, alpha release
Hey HN, at Ahrefs we have been working on an online book that hopefully helps React developers get up and running with Melange, an OCaml to JavaScript compiler. You can read more about Melange here: https://melange.re/.
There are still a few chapters that we'd like to add before considering it "complete", but it might be already helpful for some folks out there, that's why we decided to publish it early.
The book uses Reason syntax to implement React components using ReasonReact components. You can read more about both in:
https://reasonml.github.io/
-
Reason and React Meta-Frameworks
In my previous post on trying to use the NextJS App Router and Reason I described some of the problems and limitations of their compatibility with one another. With the release of Melange 2 I decided to see if the new features of Melange 2 could help to increase the compatibility of Reason and the NextJS App Router. I have also documented some of the things learnt after trying Melange (v1) with Astro and Remix.
- GitHub - melange-re/melange: A mixture of tooling combined to produce JavaScript from OCaml & Reason
-
OCaml 5.0 Alpha Release
So it's Reason, not ReasonML which the umbrella project's name, and Rescript is a imcompatible syntax split from the Bucklescript team (that previously transpiled Reason to JS). Bucklescript's new name is... Rescript.
But not everyone agrees with the split and work is being done on Melange to replace Bucklescript : https://github.com/melange-re/melange
Ultimately JsOfOcaml can directly transpile Ocaml to JS.
-
Question about the Reason project in general
In reality, most folks that developed BuckleScript frontends with ReasonML switched to ReScript syntax and are happy with it. Some felt more friction because of their reliance on PPXes or FP-heavy libraries (like Relude) and those people tend to use the Melange fork of BuckleScript or they switched to js_of_ocaml.
-
From TypeScript to ReScript
There is a fork of ReScript that supports ReasonML syntax and with the goal of maintaining Ocaml compatibility: https://github.com/melange-re/melange.
-
From object-oriented JS to functional ReScript
There's also a fork of BuckleScript/ReScript called Melange that guts its build system so that instead of using ninja, it works with more standard tools for the ecosystem, specifically dune and esy. In doing so they managed to also finally get the compiler off of OCaml 4.06: now it can use a newer OCaml compiler and take advantage of four years worth of language and compiler improvements.
- Are Dynamic Languages Going to Replace Static Languages? (2003)
-
Writing custom VSCode extensions in ReasonML
For OCaml and ReasonML your options are js_of_ocaml (mentioned here in ReasonML docs) or a fairly new fork of BuckleScript called melange. They differ in implementation and output, with JSOO taking intermediate bytecode generated by ocamlc and turning it into unreadable JS, vs Melange being a patched compiler that builds more human-readable JS.
vscode-ocaml-platform
-
using vscode? This issue needs 20 upvotes to get worked on
Ideally the vscode mode for OCaml should also be able to implement its own error-reporting format (assuming structured error messages from the compiler) or register its own regexes... wait a minute, does it not already do that? A quick search points to https://github.com/ocamllabs/vscode-ocaml-platform/issues/227 which suggests that the vscode-ocaml-platform plugin does include regexps to parse OCaml file locations. So are you sure this needs an upstream fix?
-
OCaml 5 Dev Experience?
You're looking at an old repo, I'm pretty sure the VS Code extension works with OCaml 5.0.
-
Is there a modern IDE with good support for OCaml?
Out of curiosity I went to look at your issue: https://github.com/ocamllabs/vscode-ocaml-platform/issues/1020
-
Writing custom VSCode extensions in ReasonML
The main OCaml VSCode extension is written in OCaml: https://github.com/ocamllabs/vscode-ocaml-platform so you can just use the same build system and add the ReasonML preprocessor (?)
What are some alternatives?
js_of_ocaml - Compiler from OCaml to Javascript.
multicore-opam - OPAM repo for OCaml multicore development
reason - Simple, fast & type safe code that leverages the JavaScript & OCaml ecosystems
ionide-vscode-fsharp - VS Code plugin for F# development
rescript - ReScript is a robustly typed language that compiles to efficient and human-readable JavaScript.
ocaml - The core OCaml system: compilers, runtime system, base libraries
haxe - Haxe - The Cross-Platform Toolkit
genType - Auto generation of idiomatic bindings between Reason and JavaScript: either vanilla or typed with TypeScript/FlowType.
dune - A composable build system for OCaml.
scriptum - No-Frills Functional Programming Lib Augmenting Javascript/Node.js
Nim - Nim is a statically typed compiled systems programming language. It combines successful concepts from mature languages like Python, Ada and Modula. Its design focuses on efficiency, expressiveness, and elegance (in that order of priority).
lwt - OCaml promises and concurrent I/O