It's a very comprehensive framework that solves many problems elegantly and completely. It also has a large API surface and sacrifices simplicity for power. More info here: youtu.be/9FGaKfA5xR8?...

If you're new to OCaml maybe start with something simpler and ad-hoc like Dream/Melange.

Would be great to fix this upstream and specialise global compare-like functions for ints at some point!

I, personally, also find them super convenient. But, when introducing newcomers to OCaml from scratch, I think presenting things gradually works best. Really depends on the context, but for someone just exploring the language there's a complexity budget they're willing to pay.

One aspect I find important for beginners is just to ignore some problems and get things done quickly :)

Worrying about the edge cases/performance of poly compare, sexp and ppx is a recipe for frustration.

Base is definitely a better default for production code, of course!

It's a devising opinion, but I would recommend sticking to the standard library when learning the language. For slightly fancier data structures consider Containers, which is fairly lightweight and unopinionated. Base is very well-designed but does not focus on simplicity.

Something like this should work and give you a sorted set of tuples.

Agreed.. But also, if the error was presented in the reverse order it would make so much more sense.

I had an extra slide to briefly summarise the library landscape:

Sure: lwd is low-level and focuses on managing entire documents/graphs; react/note is a more classical form of continuous FRP (with signals and events); bonsai works with state machines/VDOM. None allow resource management synced with the lifetime of the views. Helix tries to offer a very simple API

Some discussion that may be helpful: github.com/ocaml/ocaml/...

Typical OCaml is much more practical than typical Haskell. The ecosystem values simplicity and ease of maintenance. The community is small but dedicated and helpful. The libraries are fewer but have excellent quality. Dune is a great build system. OCaml 5 removed the need for concurrency monads!

This was a lovely read. Thanks for explaining it all clearly! I do wish we had value-level dead code elimination. I saw an initial effort of that some time ago which looked promising.

This os looking great! What's the plan for customising the elements/components? Is it allowing users to pass custom css class names as attributes to add/override styles?