Welcome to F# Weekly,
A roundup of F# content from this past week:
- The F# development home on GitHub is now dotnet/fsharp
- Roadmap to Ionide 4.0
- May Announcements for Fable
- Visual Studio 2019 version 16.1
- WinUI 3.0 roadmap – we need your input
- Welcome to the Shell Era: Xamarin.Forms 4.0 Released
Videos & Slides
- Languages & Runtime: .NET Community Standup – May 23, 2019
- A Look at the ML.NET Model Builder – Jon Wood
- Fabulous Functional Frontends – Mark Allibone
- Domain Modeling Made Functional – Logan Mortimer
- “5M bid request/s, 2ms Max Response Time – The Road to Damascus” using F# & libuv for high performance bidding at SamsungAds/adgear.com – Wael El Oraiby
- The Dangers of Task.Factory.StartNew – Sergey Teplyakov
- Profiling .NET Core Memory Traffic using JetBrains dotMemory – Steve Gordon
- WCF vs gRPC – Mark Rendle
- Update FSharp.Core to netstandard2.0
- FsAutoComplete: Refactor Symbol Cache
- Ionide Experimental v0.2.0 (signature search and big refactoring of the project system)
- FSharp.Control.WebSockets – wraps dotnet WebSockets in FSharp friendly functions and has a ThreadSafe version.
- Thoth.Fetch – provides tried an easy to use API for working with Fable.Fetch and Thoth.Json. It supprots both manual and auto coders depending on your preferences
- Zaid-Ajaj/Elmish.AnimatedTree – An animated tree user interface made for Elmish applications
- Fabulous 0.35 with Xamarin.Forms 4.0 support
- WebSharper 4.5.5 introducing dynamic templates
- Fable.ReactNative 2.0
- XamarinForms.Reactive.FSharp 188.8.131.52
- DurableFunctions.FSharp 0.4.0
- FSharp.Control.Websockets 0.2.0
- FSharp.Control.Websockets.TPL 0.2.0
That’s all for now. Have a great week.
Previous F# Weekly edition – #20, 2019
9 thoughts on “F# Weekly #21, 2019 – Ionide 4.0 & Fable Announcements”
What is curent state of Type Providers? Does it make sense to look in this direction?
What do you mean by “to look in this direction”? Create new providers? use existing providers? improve TP SDK? Migrate old provider to .NET Core?
I’m thinking about creating new providers
Yes, TPs are not perfect and TP development is easy way. But, I think that they are in better condition than ever before. TPs works on .NET Core and on full framework, there are several TP related performance fixes in latest VS and FCS
what about wikidatatypeprovider? does it make sense?
Like this one? https://fsprojects.github.io/FSharp.Data.DbPedia/
I looked at this project and cloned it, but seems it doesn’t work, or maybe I did something wrong. But actually I prefer wikidata, not dpmedia, I think wikidata is more relalable.