#Unison is a really interesting programming language - one of the most novel I've seen in recent years https://www.unison-lang.org/docs/quickstart/

It's hard to describe, but to me it feels like some modern blend of ideas from #Haskell, #Erlang, #Smalltalk and #OCaml. I hope that it will manage to gain some traction and that I'll be able to play a bit more with it down the road.

#Unison is a really interesting programming language - one of the most novel I've seen in recent years https://www.unison-lang.org/docs/quickstart/

It's hard to describe, but to me it feels like some modern blend of ideas from #Haskell, #Erlang, #Smalltalk and #OCaml. I hope that it will manage to gain some traction and that I'll be able to play a bit more with it down the road.

The #ocaml debacle with the ginormous slop #AI / #LLM "contributions" continues! It's round two, already! Oh no. With the same outcome, predictably. This time in the #julia community.

https://discourse.julialang.org/t/ai-generated-enhancements-and-examples-for-staticcompiler-jl/134054/18

The patience of the Julia people is absolutely immense here! I've huge respect for them after reading this (and the Ocaml people, only days ago).

The fundamental issue seems to be that the guy attempting this novel approach to software development thinks the AI "understands" what it's doing. So even if showstopping nonsense in the AI-produced code is pointed out to him, he comes back with - oh well, yeah, the AI gets "lazy", or some other sort of narrative that rationalises the slop, and presumes the "AI" is, by definition, really understanding what's going on, and smart, and capable, and all that.

Will there be no end to this nonsense? Each week the patience of a new set of #FOSS maintainers will be tested? It's Groundhog Day, but with all the quirkiness and charm removed?

It's cool to observe how programming languages affect each other. Recently I've learned that `Seq.unfold` in #OCaml was "inspired" by `Seq.unfold` in its sibling F#. It in turn was inspired by `unfoldr` in #Haskell.

And there's also the pretty similar `std::iter::successors` in #Rust to consider...

The #ocaml debacle with the ginormous slop #AI / #LLM "contributions" continues! It's round two, already! Oh no. With the same outcome, predictably. This time in the #julia community.

https://discourse.julialang.org/t/ai-generated-enhancements-and-examples-for-staticcompiler-jl/134054/18

The patience of the Julia people is absolutely immense here! I've huge respect for them after reading this (and the Ocaml people, only days ago).

The fundamental issue seems to be that the guy attempting this novel approach to software development thinks the AI "understands" what it's doing. So even if showstopping nonsense in the AI-produced code is pointed out to him, he comes back with - oh well, yeah, the AI gets "lazy", or some other sort of narrative that rationalises the slop, and presumes the "AI" is, by definition, really understanding what's going on, and smart, and capable, and all that.

Will there be no end to this nonsense? Each week the patience of a new set of #FOSS maintainers will be tested? It's Groundhog Day, but with all the quirkiness and charm removed?

It's cool to observe how programming languages affect each other. Recently I've learned that `Seq.unfold` in #OCaml was "inspired" by `Seq.unfold` in its sibling F#. It in turn was inspired by `unfoldr` in #Haskell.

And there's also the pretty similar `std::iter::successors` in #Rust to consider...

I'm working on a toy #OCaml build system and package manager in my spare time. Here's a blog post about how it enforces package hygiene while building packages.

https://www.alicecaml.org/blog/package-hygiene-in-alice/

I'm working on a toy #OCaml build system and package manager in my spare time. Here's a blog post about how it enforces package hygiene while building packages.

https://www.alicecaml.org/blog/package-hygiene-in-alice/

Interesting new experimental build system for #ocaml from one of Dune's core developers:

https://www.alicecaml.org/about/

Linux mode setting, from the comfort of OCaml

https://roscidus.com/blog/blog/2025/11/16/libdrm-ocaml/

#HackerNews #Linux #OCaml #libdrm #mode-setting #programming

I Love OCaml

https://mccd.space/posts/ocaml-the-worlds-best/

#HackerNews #I #Love #OCaml #OCaml #Programming #Functional #Programming #Tech #Community #Programming #Languages

We chose OCaml to write Stategraph

https://stategraph.dev/blog/why-we-chose-ocaml

#HackerNews #OCaml #Stategraph #programming #functionalprogramming #softwaredevelopment

Pain Points of OCaml

https://quamserena.com/2025-11-03/pain-points-of-ocaml

#HackerNews #OCaml #PainPoints #FunctionalProgramming #DeveloperInsights

Huh, I was so used to always using Jane Street's Base when writing #ocaml that I haven't looked at the stdlib in a very long time. Turns out it's pretty usable now. Just updated some code and it wasn't that much effort, especially thanks to the ListLabels module. Good to keep in mind going forward.

I like consistent colors in my terminal and I like #OCaml, so I threw together a quick Nord color scheme for utop:

https://git.sr.ht/~citizen428/nord-utop

I have now also resurrected the other old #ocaml article and converted the code examples from #reasonml:

https://citizen428.net/blog/ocaml-module-functors/

Note that this was originally written for an audience of mostly OO programmers, not FP aficionados, so it may occasionally be a bit loose with terminology.

I have another #ocaml article that is no longer available online since the magazine it was written for has shut down. However, it uses #reasonml syntax. Does anyone still use that, or should I convert the examples to OCaml and update the text?

A couple of years ago I wrote an article about #ocaml extension points/PPX for a magazine that no longer exists. It's been offline for a while now and is unlikely to ever come back, so I decided to republish it on my blog:

https://citizen428.net/blog/introduction-ocaml-extension-points/

Operator Lookup

https://www.craigfe.io/operator-lookup/

Very useful #ocaml tool.

Every couple of years I seem to briefly develop a crush on #ocaml. Now seems to be such a time again, triggered by the 5.4 release announcements. This post is very informative if you're not (too) familiar with the language.

https://xvw.lol/en/articles/why-ocaml.html