https://fosdem.org/2026/news/2025-11-16-accepted-stands/# #FOSDEM : I will be back at #FOSDEM2026 , ask me about #XcpNg
or to my new colleagues from @vates , we will hang around the #Xen community
This can only happens at #FOSDEM unexpected meeting with #OSHW @braillerap and |Lupin| an #ocaml engineer joing @vates in may
I'm glad to announce a new project from robur, a KV-store which is able to work as an unikernel and in parallel in #OCaml. We especially use it to index our emails. You can see more here: https://blog.robur.coop/articles/2025-18-12-bancos.html
I'm glad to announce a new project from robur, a KV-store which is able to work as an unikernel and in parallel in #OCaml. We especially use it to index our emails. You can see more here: https://blog.robur.coop/articles/2025-18-12-bancos.html
I currently have some availability for an additional freelance client.
I've been doing #ruby since 2004 or so, and #rails since v1.
I'm also reasonably competent in #JS/#TS (more BE than FE), #python, and #go. If FP is your thing, I can do #elixir, #gleam, or #ocaml, though of the three, I only used Elixir (Phoenix) in production.
All that said, almost all of my recent contracts were for Fractional CTO/Engineering Lead roles.
If any of that sounds interesting, HMU.
#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.
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?
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.
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?
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.
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.
Interesting new experimental build system for #ocaml from one of Dune's core developers:
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
We chose OCaml to write Stategraph
https://stategraph.dev/blog/why-we-chose-ocaml
#HackerNews #OCaml #Stategraph #programming #functionalprogramming #softwaredevelopment
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:
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.
![The following example code in a utop session show in the Nord colorscheme.
# let rec sum = function
| [] -> 0
| hd :: tl -> hd + sum tl;;
val sum : int list -> int = <fun>
# #show sum;;
val sum : int list -> int
# "Hello, " ^ "OCaml " ^ "World!";;
- : string = "Hello, OCaml World!"
# 1/0;;
Exception: Division_by_zero.
# 1 + "string";;
Error: This constant has type string but an expression was expected of type int](https://assets.chaos.social/media_attachments/files/115/458/721/336/336/306/original/7af3206dd425fc17.png)