dlidstrom.bsky.social
@dlidstrom.bsky.social
This page is a nice piece of work, IMO: camilotk.github.io/fsharp-by-ex...
No need to start with 400+ pages books. The domain name could be better (more prominent) though.
F# by Example
camilotk.github.io
November 21, 2025 at 7:19 AM
Looks like a nice book indeed. My only issue is that it has 336 pages so it is quite a bit to take in. I think F# basics can be explained in a fraction of that, just to get people started.
November 11, 2025 at 12:08 PM
Learning F# (or any technology really) is so much easier now thanks to ChatGPT. My tip is to be careful with F# for fun and profit. While interesting it also has lots of parts which are not really useful. What’s missing is a more approachable, simple, F# for C# devs tutorial.
November 11, 2025 at 8:10 AM
Still trying to format your code?
November 7, 2025 at 1:05 PM
From an outside perspective it didn’t look like the last minute democratic nominee was a particularly good choice.
November 4, 2025 at 11:26 AM
Type classes separate structure from behaviour. In F# we can easily customise behaviour in many ways. Easiest is to pass a function, other ways are more involved (function dictionaries, interfaces). Scala devs can customise ToString implementations on a case-by-case basis. Just as we can 👍🏻
November 4, 2025 at 8:36 AM
Where’s the Prague team?
October 31, 2025 at 8:19 AM
Computation expressions to the rescue (what an invention!). Check out this slick implementation: github.com/brianrourkeb...
This one should not go under the radar 💪🏻
GitHub - brianrourkeboll/FSharp.AspNetCore.WebAppBuilder: An F# computation expression for succinctly defining ASP.NET Core web apps, including support for minimal APIs.
An F# computation expression for succinctly defining ASP.NET Core web apps, including support for minimal APIs. - brianrourkeboll/FSharp.AspNetCore.WebAppBuilder
github.com
October 16, 2025 at 12:01 PM
Most of my files are around 100 lines, many less than that. Some reach 400 lines. Not concerned too much as I trust the language when refactoring. What I struggle with sometimes is where to place types. Sometimes I wish F# supported tree structured module dependencies to reduce type visibility.
October 14, 2025 at 2:05 PM
Hi Seegey, your fine blog keeps asking me this every I want to read your latest post.
October 8, 2025 at 10:27 AM
Wow that is a lot to take in! I’ve got a few workers I’ve (somewhat painfully) implemented in JavaScript. This opens up an entirely new front!
September 30, 2025 at 9:51 PM
Nice solution 👍🏻
September 30, 2025 at 12:07 PM
Both have strengths and weaknesses (yes F# too has weaknesses, in particular harder to understand). I don’t like dotnet in-fighting. If you’re only doing F# or C# you’re missing out (IMHO). They could have compared C#/F# combo with Java instead.
September 23, 2025 at 7:05 AM
It’s interesting that monads keep coming up around F#. I can only find it mentioned in one of the official pages on F# (on CE naturally, but only in passing).
September 16, 2025 at 1:19 PM
Maybe there’s an AI for that?
August 27, 2025 at 7:12 PM
I guess it is due to C legacy: first saying what it is, then its name. Just typing in that order immediately invokes imperative mindset (I want memory of this type). Type after matches how variables are declared in math. It’s like a structure applied on top of my variables
August 26, 2025 at 2:04 PM
A language designer can probably explain better, but to me ”Type t” feels imperative, while ”t : Type” feels declarative. Unified syntax and optional parenthesis would be nice to have in C# 😊
August 26, 2025 at 9:32 AM
How are democrats identified?
August 21, 2025 at 8:44 AM
Currently in my homelab. Exposed using Cloudflare tunnels. Love it! Important stuff is backed up to DigitalOcean.
August 20, 2025 at 5:15 AM
I do some programming in F#. Here’s what I regularly use:
- computation expressions: Yes
- Railways: Rarely…
- Partial application and currying: Rarely
- Monads: Implicitly through CE’s
- Discriminated unions: All the time
- Pattern matching: Yes!
- Type-safe programming: Yes, straight from db!
August 20, 2025 at 5:14 AM
Nice example. Only issue with pipelining is that sometimes we want to inspect intermediate results. This requires modifying the pipeline while it comes naturally in the other one.
August 13, 2025 at 9:53 AM
It has been working fine for smaller greenfield projects. I got a lot of help with some complex functions. For my larger projects I find it less appealing.
July 22, 2025 at 3:33 PM
I'm living in the real land of the free.
July 6, 2025 at 8:37 AM