rponte

-- Let's say you have a table full of work:

CREATE TABLE tasks (
       id UUID PRIMARY KEY NOT NULL DEFAULT gen_random_uuid(),
       status TEXT NOT NULL DEFAULT 'pending',
       payload JSON NOT NULL, -- or just have meaningful columns!
       created_at TIMESTAMP NOT NULL DEFAULT NOW()
);

mbuhot

namespace System.Text.Json

open System
open System.Collections.Generic
open System.Text.Json.Serialization

// Converts Option<T> to/from JSON by projecting to null or T
type OptionValueConverter<'T>() =
    inherit JsonConverter<'T option>()

ninjarobot

My Road to F#

I came from the OOP world, most of my professional work was in Java or C#. The languages were similar, and I could use them interchangably as I built software in each of them for several years. With enough experience in both, I was comfortable with either ecosystem and could generally be productive in either. Sometimes the job required one or the other. Sometimes the target OS constrained my choice to Java, which frustrated me a bit, because the languages were so similar, why would the runtime try to restrict a choice? I enjoyed writing server applications on Unix in college, and Linux afterwards, because the machines were so easy to configure compared to Windows machines that took a few hours to install and configure to get my software running. On Linux, I could type a handful of commands into a newly installed system and be up and running.

Sometime around 2005, Java had stagnated while C# was flourishing. They both released generics, but then C# came out with new features like