And if you do, check out Sury (github.com/DZakh/sury) and serde_derive (github.com/alex35mil/se...)
28.02.2026 19:44
👍 2
🔁 0
💬 0
📌 0
And if you do, check out Sury (github.com/DZakh/sury) and serde_derive (github.com/alex35mil/se...)
Try the new reactive code analysis if you haven't yet:
rescript-lang.org/blog/reactiv...
hi folks! long time no see. i’m officially open to work again, primarily interested in the dx + devtools + ai space
if anyone needs a principal engineer or technical product manager with 16+ years in the industry, my DMs are open!
linkedin.com/in/leostera
github.com/leostera
If this works out, I will use it for my blog!
Star history plot of the GitHub repositories "rescript-lang/rescript" and "elm/compiler".
Need more stars
I decided to extract a test framework I've been using across my #rescript projects into its own package.
Zekr is a very simple and minimal test framework, but easy to use. Let me know what you think if you try it out: github.com/brnrdog/zekr
Still on fire. Still shipping.
ReScript v13.0.0-alpha.1 is now on npm.
github.com/rescript-lan...
For those interested, I released two new versions of rescript-signals with a bunch of performance improvements and a benchmark script:
github.com/brnrdog/resc...
#rescript #signals
The embed-lang approach I linked above has the huge advantage that code-generators can be implemented in any language, not just OCaml.
We won't remove ppx support anytime soon though, there are still many rescript-specific ppxes out there which we would not want to break like the built-in react ppx, ppx-spice, sury (aka rescript-schema), etc.
github.com/rescript-lan...
For at least some applications of ppx.
We are about to sunset the ReScript legacy build system. If you’re stuck, can’t upgrade, or worried about migration, we want to hear from you!
Join the discussion: forum.rescript-lang.org/t/ann-sunset...
On the other hand:
Pic of developer in front of PC feeling calm, as they use ReScript at work.
Totally agree!
Here is a gem from the ReScript Developer Discord that illustrates it. (by @tsnobip.bsky.social)
We won't become SlopScript. Not on my watch.
github.com/rescript-lan...
This now emits the correct output for my ReScript libraries.
Try with yours, and tell me what you think.
ReScript has a wikipedia page now.
Thank you!!!
ada, agda, asm, awk, bash, batch, c, c-sharp, caddy, capnp, clojure, cmake, commonlisp, cpp, css, d, dart, devicetree, diff, dockerfile, dot, elisp, elixir, elm, erlang, fish, fsharp, gleam, glsl, go, graphql, haskell, hcl, hlsl, html, idris, ini, java, javascript, jinja2, jq, json, julia, kdl, lean, lua, markdown, matlab, meson, nginx, ninja, nix, objc, perl, php, postscript, powershell, prolog, python, query, r, rescript, ron, ruby, rust, scala, scss, sparql, sql, ssh-config, starlark, svelte, textproto, thrift, tlaplus, toml, typescript, typst, uiua, vb, verilog, vhdl, vim, vue, wasm, x86asm, xml, yaml, yuri, zig, zsh.
👋 PSA: if you have a codebase
- that's MIT-licensed (or more permissive)
- in any of the languages below
- and you would like it to be featured in a demo
reply with the language identifier + link to a git repo 🙏
ReScript 12 is here!
A major step toward a leaner, faster, simpler toolchain.
This release refines the language and embraces ReScript’s own identity.
Blog: rescript-lang.org/blog/release...
Notes: github.com/rescript-lan...
Huge thanks to everyone who helped move ReScript forward.
Wooohooo!
I am still taking my time with Act 2, I try to explore everything. So many optional areas and bosses.
6. Yes, the build system is also more closely connected to our editor tooling, it emits some useful metadata that helps improve error messages.
7. We might have just been to dumb understand the whole feature set of ninja 😅
4. Rust has already a great JS tooling ecosystem, e.g. for npm dependency resolving stuff
5. ReScript generally is about owning the whole stack and vertical integration in order to deliver the best DX. So we just have to own everything.
1. The CLI was in JS, is now all Rust.
2. The binary that wrote the ninja build rules was in OCaml, now that functionality is done in a Rust binary
3. The watcher (also OCaml) was somewhat hard to understand and couldn't handle npm workspace repos, rearchitecting was necessary anyways
