I like using a record with a single field because it’s easier to unwrap the value, but single case DU is a common approach.
11.03.2026 22:12
👍 2
🔁 0
💬 0
📌 0
I like using a record with a single field because it’s easier to unwrap the value, but single case DU is a common approach.
Not exactly. SourceDjinn came out of the internals I built for Serde.FS to get that "attribute-and-go" C# source generator experience.
Myriad definitely influenced the direction, though — you really can’t think about F# metaprogramming without thinking of Myriad!
The wait is over! Fable 5 Release Candidate is officially here.
After a year of hard work from the community, we're bringing you:
✨ .NET 10 & F# 10 support
🐍 A massive Python update (now powered by a Rust core & PyPI!)
🌐 Cleaner JS/TS Pojo bindings
fable.io/blog/2026/20...
#fsharp #fablecompiler
Serde.FS.Json is the first backend in the new Serde.FS ecosystem — fast, reflection‑free JSON for F#.
Powered by FSharp.SourceDjinn, a small engine for building F# source generators.
github.com/fs-djinn
#fsharp
As for ecosystem size, I think this may be the golden era for F# because the people using it do so because we love the language. We like making OSS projects for it, and it's now easier than ever for the community to create awesome stuff for the F# ecosystem -- which is exactly what is happening now.
I do all my work in F# and still get the warm glow. Simple functions as DSLs + small interim types allows me to design declarative workflow-specific pipelines that would be imperative in other langs. But as you move away from the code, perhaps it doesn't matter.
SqlHydra v3.5 released with new query functionality for SQL Server. #fsharp
github.com/JordanMarr/S...
Well-articulated points.
Opus 4.6 is a savant junior coder. I just watched it try to add an `Errors` property to my response -- completely ignoring the fact that the function was wrapped in an `asyncResult` CE. 🤦♂️
Around 3 Years later but Migrondi v1 release is out!
#dotnet #fsharp #migrondi
FSharp.SystemCommandLine v2.1 provides a more declarative way to inject services alongside CLI arguments and options.
github.com/JordanMarr/F... #fsharp
I've always said that "typing is not the bottleneck."
Thinking through the problem, use cases, edge cases and designing invariants is.
SqlHydra - v3.4 is out today. It is a rollup of the last two releases. Lots of nice, new features and some deprecated ones to help transition into an upcoming v4.0. #fsharp
github.com/JordanMarr/S...
Big update for the Fable + Lit ecosystem!
✨ Fable.Lit.Dsl
✨ Fable.Lit.Dsl.Shoelace
✨ Fullstack template update (.NET 10 + Fable 5)
#fsharp #webcomponents #lit
github.com/JordanMarr/f...
🚀 Agent.NET has evolved significantly since the alpha.1 announcement — alpha.2 and now alpha.3 bring proper MAF execution, symmetrical InProcess/Durable workflows, and a more cohesive workflow CE with ROP built in.
Full release history:
github.com/JordanMarr/A...
#fsharp #dotnet #aiagents
It's kind of funny that due to AI/LLMs these days another metric to rate #programming languages on has become "token efficiency".
On the bright side - some of the beloved languages like #Clojure, #Ruby, #FSharp and #OCaml fared pretty well due to their expressive and compact syntax.
A beautiful F# library for building AI agents on .NET:
• Quotation-based tool discovery
• Pipeline-style agent composition
• Computation expressions for workflows
• Railway-oriented error handling
F# deserves a place in the agent era — and this is my contribution.
#fsharp #dotnet
SqlHydra v3.2 big release today that builds on yesterday's release! Now includes DB-specific functions for all 5 supported DBs, custom functions, and adds .NET 10 support.
Samples included in the release notes.
github.com/JordanMarr/S... #fsharp
SqlHydra.Query v3.1.0 adds support for calling SQL functions!
github.com/JordanMarr/S... #fsharp
My FS Advent post for Dec 22, 2025. 🎄✨☕
Thanks to @sergeytihon.com for keeping the F# community buzzing along year after year!
jordanmarr.github.io/fsharp/cloud... #FsAdvent #fsharp
Sneak peek of new #fsharp side project...
Fable + Desktop 🤔
All day, every day!
I don’t notice much difference between my F# and C# project build times.
But I’ve heard some type provider libraries can slow it down though.
Great tips for getting real value out of FSI! I love the idea of creating bootstrap fsx scripts to preload modules. That alone will make FSI much more useful for non-trivial exploration.
And the MCP server obviously takes it to the next level as well.
Frogs ’n Flies was straight up my favorite Atari game back in the day!
If you hit the expert mode switch on the console, you could very precisely control your frog’s jump!
Bringing it back full circle in 2025 with the FP FrogInterpreter! ❤️🐸
Mark Seemann did a great talk years ago where he showed examples of some really gnarly method headers in C# to emphasize how type inference is almost a requirement for FP.
Would love to watch it again if I could find it.
Right?! Even though “C# has all the FP features from F#”, not having type inference makes things that are trivial in F# so ugly in C# that most will never use it.
t really bothers me having to type in the full tuple return type and predicate function type in C#.
To each their own but #fsharp type inference just makes me happy.
Fable 4 and Fable 5, both got a new release to make them work with .NET 10 🎉 #fsharp #fablecompiler
That seems like it could work pretty well. I would think that giving it an example bindings project with a style that you like and then pointing it to API docs could work pretty well.
