I wrote a short article about the origin of the pipeline operator (|>) https://batsov.com/articles/2025/05/22/the-origin-of-the-pipeline-operator/ You've probably seen it in #OCaml, #Elixir and #FSharp.

TIL #fsharp provides these native operators:

let (:=) cell value = cell.contents <- value

let inline (||>) (arg1, arg2) func = func arg1 arg2

let inline (|||>) (arg1, arg2, arg3) func = func arg1 arg2 arg3

For those familiar on the matter…

What's your preferred syntax for the pipeline operator?

Current state: writing a series of articles about Monadic Parser Combinators in #fsharp

When #AI encounters #Fsharp ..... just #python :(

Blogged: https://brandewinder.com/2025/04/02/delaunay-bowyer-watson-algorithm/

Where I finish implementing the core of the Bowyer-Watson algorithm in #fsharp and get a pretty Delaunay triangulation, but find out there is a bug somewhere :(

It's always sad when reading comments on #fp languages and people saying "I tried #ocaml, #haskell, #fsharp... and don't like because X", which shows they are interested but then also say "I looked at #scala and it looked complex so I didn't even try it and ran away" ...

People, if you can do it in those languages, you can do it in scala. It's the most popular and used in production fp language in the world!

Thanks for coming to my teg talk

Over the weekend I wrote an article dedicated to my recent experience playing with #FSharp https://batsov.com/articles/2025/03/30/why-fsharp/

I hope that it will inspire a few more people to check out this really cool language!

Why F#?

https://batsov.com/articles/2025/03/30/why-fsharp/

#movieLinesInCode

type Pill =
| Blue
| Red

let choose pill =
match pill with
| Blue ->
let rec loop () = loop ()
loop ()
| Red -> Environment.Exit(0)

Today I came across a cool job board highlighting job openings for more "exotic" programming languages (think #Clojure, #FSharp, #Elixir, etc) - https://beyond-tabs.com/

It's always nice to see such initiatives and I hope it will helpful someone land a dream job in their favorite programming language.

#fsharp does not support function overload. Which would come in very handy for implementing Monad Transformers.

F#+ supports both.

I was stubborn as a mule about wanting to understand how it worked, and I eventually got to the same code implemented in F#+. It's horribly convoluted.

I guess I'm soon writing a blob post with all the steps to get there.

After an annoying work day that started with waking up unpleasantly early to attend a meeting which did not take place, and continued along the same vein, I needed to feel like I actually did something today, and wrote some more Delaunay triangulation code. It ended up much easier than what I thought - it's actually almost done. #fsharp

Unlocking the Power of F#: A Developer's Guide to Functional Programming

Dive into the world of functional programming with F#, a versatile language that can transform how you approach software development. This article explores the fundamentals of F#, its practical applic...

https://news.lavx.hu/article/unlocking-the-power-of-f-a-developer-s-guide-to-functional-programming

I’m fascinated by Free Monads. #fsharp

In the attempt to grasp monad transformers, I'm reading Grokking Monads by Matt Thornton (can't find him here on Mastodon)

It's a very well written series, #fsharp based, and I would recommend it as a first read about monads.

https://dev.to/choc13/grokking-monads-in-f-3j7f

Harnessing F# for React Development: NPM Integration Made Easy

Dive into the world of F# and discover how to seamlessly integrate npm packages into your React applications. This article demystifies the process, showcasing the power of F# combined with the vast ec...

https://news.lavx.hu/article/harnessing-f-for-react-development-npm-integration-made-easy

The trait that I initially hated the most about #fsharp, the compilation order, quickly turned out to be among those I love the most. It forces me to think and to care about design.

Lovely.