Why am I so enthusiastic about F#?

I'm suddenly really passionate about F#. This is new as of ~3 weeks ago.
Why?

• Why F#?
• I don't know about you, but more and more of the code I see in the industry is more procedural and barely qualifies as OOP, let alone SOLID OOP
• SOLID: the next step is Functional- Mark Seemann (Writer of Dependency Injection in .Net)
• Dependency Injection is not even relevant in F#
• When and where do we do our domain modelling in C#?
• Why are we deciding all these things in  C# first?
• DAL (or ORM)
• To Write tests or not
• the db implementation
• the ui
• service layer
• Is it any wonder problem domain logic is found everywhere from the ui, to the ORM layer, to the persistence code?
• Domain modelling with the F# type system - Scott Wlaschin - NDC (Norway Developer's Conference)
• Video
• slides
• What can C# do that F# can't? Null Reference Exception!
• Smashing the Myth: Why You Must Learn F# - Even If You Aren’t Writing Rocket Science Apps
• What kind of boilerplate required cruft is there in C# that you might not realize?
• Does the language you use make a difference (C# vs F#) 
• What kind of boilerplate cruft might you find in OCaml compared to F#?
• In 1 year they go from 345k lines of code in OCaml and 171k in F# and now just 261k in F#, no more OCaml 
• F# not permitted at work?
• 26 low risk ways to use F# at work