do you think its problematic?

for me the biggest misconception is that you need to know the intrinsics of monads to be able to use them.

i likely know less about the rules of my mother tongue than people who've studied it, yet i'm able to use it fluently

absolutely a blast to use, the only issues i've had are lsp-related but haven't really tried to debug

US green card granted

ah right, i think understand now. you were thinking more validating against the schema while teej's approach is essentially using ocaml as the source of truth

teej is building something like this where the queries refer to user defined types and give inline type errors (etc)

x.com/teej_dv/stat...

fwiw, reason supports named operators `let (let.bind) = Option.bind` (not sure the correct syntax but something along those lines at least), which i miss in ocaml

`let.bind x = …`
vs
`let* x = …`

hard agree, it's rad

hazel.org's syntax imo combines the best of both worlds

bucklescript used |. for piping (pipe first) previously iirc

ngl, i don't hate it, feels like there'd be a lot of ambiguity to handle when parsing though

List.(
user.books
. map do_smth
. keep do_smth
)

for reasons unknown, i wrote a little article on getting to know ocaml by writing a simple diff checker

sketch.sh/s/i4HpNY61ih...

absolutely yes!

Hazel is really cool

haha, we know

sounds like you're carrying quite the bladder

they have instructions for lsp-setup on the preview page as well

not sure how helfpul, but using the developer preview i use this, i'm sure there's some other way, but ocaml-lsp-server is installed automatically

`dune tools exec ocamllsp —`
`dune tools exec ocamformat —`

preview.dune.build

can very much recommend it, no more opam switches etc

GitHub - lessp/react-ml-minimal-template Contribute to lessp/react-ml-minimal-template development by creating an account on GitHub.

wanted an extremly barebones setup to write ocaml + react (to js), perhaps it can be useful for someone else :) or ”get up and running with ocaml + react.js in under a minute”

github.com/lessp/react-...

the key for me here is that you can communicate that with more finesse and empathy, we're not robots yet :)

”hmm, have you tried looking at this from another angle? perhaps …”

yeah, diffing the two

(* a.txt *)
foo

(* b.txt *)
bar

diff a b
- foo
+ bar

diff checker

Antonio 🥹 true MVP

Tablecloth has a fantastic API imo, would push for that

it's priced in

ocaml hype train confirmed

Sabine Useocaml, don't even have to change your bluesky handle

go with your gut, and ”cross that bridge when you come to it” imo

ending up in these decision trees is a drag, i find it better to just go with an option even if it turns out it's not the best one :)

yes, and the error messages are usually quite a mouthful