Format code

Author: nojaf

src/layouts/Layout.astro

@@ -52,8 +52,8 @@ import Navigation from "../components/Navigation.astro";
 <style is:global>
   :root {
     --monospace-font: "Fira Code", monospace;
-    --system-font: Avenir, Montserrat, Corbel, "URW Gothic", source-sans-pro,
-      sans-serif;
+    --system-font:
+      Avenir, Montserrat, Corbel, "URW Gothic", source-sans-pro, sans-serif;
 
     --spacing-50: 4px;
     --spacing-100: 8px;

src/sessions/2025-05-16.md

@@ -0,0 +1,25 @@
+---
+title: "FSharp.Core.Extended"
+preview: "FSharp.Core.Extended"
+isDraft: true
+date: 2025-05-16T13:00:00.000Z
+id: "2025/05/23"
+champion: "Vlad Zarytovskii"
+zoomLink: ""
+zoomPasscode: "extended"
+issueLink: ""
+company: "Microsoft"
+youtubeId: ""
+---
+
+## Topic
+
+F# has always prioritized backward compatibility, making migration paths straightforward. This is why [FSharp.Core](https://www.nuget.org/packages/FSharp.Core) targets `netstandard2.0`, ensuring broad compatibility across various .NET runtimes.
+
+However, more recent .NET runtime versions introduce new performance opportunities that `netstandard2.0` can't fully leverage – think new primitives like `Span<'T>` or `ValueOption<'T>`. This is where [FSharp.Core.Extended](https://github.com/vzarytovskii/FSharp.Core.Extended) comes in. This library aims to be a drop-in _alternative_ for `FSharp.Core`, offering functions that are generally faster and more flexible by utilizing these newer features. It's worth noting that while it's a drop-in _replacement_ in terms of providing similar functionality, these performance gains might introduce runtime or compile-time incompatibilities compared to the original `FSharp.Core`.
+
+We're excited to have Vlad, the former guardian of F#, here to talk about this interesting project!
+
+## Champion
+
+- [Vlad Zarytovskii](https://github.com/vzarytovskii)