dotNET (OK, C#) gets union types

Microsoft’s C# language is finally getting union types in the .NET 11 preview—a long-requested feature that basically lets one value cleanly stand for different kinds of things without turning your code into a mystery box. The blog post frames it as a big quality-of-life upgrade, especially for handling “success or error” situations and mixed data types like Windows, Linux, or Mac entries. In plain English: developers can now describe messy real-world data more directly, instead of relying on awkward workarounds.

But the real fireworks are in the comments, where this news instantly turned into a language rivalry reunion tour. One camp basically shouted, “F# did it first,” with munchler rolling their eyes that C# keeps getting the spotlight while its functional-programming sibling keeps being the trendsetter. Another group was genuinely thrilled—not because they want flashy new syntax, but because it should make C# play nicer with other languages and systems.

Then came the doom-posting. Quarrelsome summed up the anxiety with a very relatable fear: if code is confusing now, what happens when developers get a brand-new toy? Others zoomed in on edge-case limitations, like whether some two-of-the-same-type combinations will work at all. And in classic comment-thread fashion, one person used the moment to ask if anyone even uses .NET outside Windows anymore. So yes, C# got a shiny new feature—but the community reaction was a perfect blend of victory lap, sibling jealousy, and “this will absolutely make my coworker’s code worse” panic.