F# Weekly #23, 2022 - Fabulous 2.0, FsPdf and F# Weekly Reading

[sergey_tihon]

Welcome to F# Weekly,

A roundup of F# content from this past week:

News

• Announcing .NET Machine Learning Notebook Series - Microsoft Tech Community
• Incremental ASP.NET to ASP.NET Core Migration - .NET Blog (microsoft.com)
• Improved doc management personalization - Visual Studio Blog (microsoft.com)
• Resources for F# Onboarding (github.com)

Fabulous

Videos and Slides

• Fast F#: Topological Sort Part 2 - Domains and Collections - YouTube
• Working with GraphQL services from F# - Zaid Ajaj - NDC Oslo 2021 - YouTube
• Reliable Client Server Data Transport for F# web applications - Zaid Ajaj - NDC Oslo 2021 - YouTube
• F# Weekly Reading, 2022 #22 - YouTube
• Build native apps for any device with .NET and Visual Studio (microsoft.com)
• .NET MAUI - Updates and Roadmap (microsoft.com)
• On .NET Live - Building Low-Latency Distributed Systems with Akka.NET - YouTube

Blogs

• Introducing Fabulous 2.0 - Timothé Larivière
• Use OData with fsharp and swagger in frontend and backend - slaveOftime
• Real enterprise application with Fun.Blazor - slaveOftime
• Azure Container Apps with SAFE stack and Farmer - Ryan Palmer

F# vNext

• Remove unused FCS support for compiling from ASTs · Issue #13242 · dotnet/fsharp (github.com)
• Difference of compilation time between 13 000 "static member" and 13 000 "let binding" · Issue #13218
• F# language suggestions:
  • Add a String-focussed Computation Expression Syntax · Issue #1149
  • Add Active Patterns for doing String Comparison · Issue #1148

Don Syme

Highlighted projects

• palladin/Higher: A lightweight library of abstractions for Higher-kinded programming in F#
• MangelMaxime/template-gitpod-fable-3-vite-react

New Releases

• Fabulous 2.0
• fsautocomplete 0.54.0
• Fun.OData 2.1.0
• FsPdf 0.0.1

Don Syme

That’s all for now. Have a great week.

If you want to help keep F# Weekly going, click here to jazz me with Coffee!

 

[kspeakman]

@Tarmil The Literal Provider looks awesome! I’ll definitely be checking it out.

My use case is for view table revisions. We keep a Revision integer literal in the code. When the code gets deployed, the code revision is compared to the stored revision. If different, the view table will be dropped and rebuilt automatically. Right now we update the revision manually, which is easy to forget.

Thank you!