You got FP in my Enterprise!
summary
F# is used to implement F# and the tools are packaged as a compiler binary for .NET Core, source builds, .NET Framework, and Mono — compiler packaged four ways. Compatibility is king: strict backward and binary compatibility, soft then hard deprecation, and a new language version flag for preview features. Tooling runs as a long‑lived server so allocations and the large object heap cause UI pauses; partial application increases allocations; PDB emission, computation expressions for cancelable async, SLAs, and the VS Code extension with 1.3M downloads are concrete engineering realities.
AI-written summary · about
chapters (30)
- 0:00Introduction
- 2:03FP the language
- 2:32ML style
- 7:10Fsharp
- 9:26Fsharp at Microsoft
- 10:51Fsharp Compiler
- 13:33Fsharp Core
- 14:38Commandline Tools
- 15:12Editor Tools
- 16:11Visual Studio Code
- 17:18Documentation
- 18:33Compatibility
- 20:42Core Library
- 21:51Not Supported
- 23:09Deprecation
- 25:08F Sharp 45
- 26:48Language Version Flag
- 28:03Language Evolution
- 31:08Performance
- 33:20Compiler Performance
- 35:24Editor tooling performance
- 37:38Architecture is not perfect
- 39:26Syntax vs Semantics
- 41:17Computation Expressions
- 42:07Visual Studio
- 42:48Navigational Symbols
- 44:42Summary
- 45:37Overall takeaways
- 51:03Fsharp tensorflow
- 55:03Fstar
related talks
01h 00mF# for C# programmers
01h 01mStay with C# or switch to F#? Let's fight! Let's vote!
41mF# in Social Gaming
51mMaking a difference in open-source
43mThe Big Problems Facing Functional Programming & a Possible Solution
42mIntroducing A Functional Language At Work
40mWhat the F(p) is Kotlin?
39mTyped FP on the Job Why Bother