4 ms·
Have you tried employing either in any recent time? Or is this just what you think is the state of affairs without contextual knowledge?
by neonsunset 2y ago
Have you tried employing either in any recent time? Or is this just what you think is the state of affairs without contextual knowledge?
- pjmlp 2y agoGood luck doing Blazor in straight F# or VB without C# glue code, does it answer?
- neonsunset 2y agoThere is, in fact, a package that does just that: https://github.com/slaveOftime/Fun.Blazor https://github.com/slaveOftime/Fun.Blazor (and there are others IIRC)
- pjmlp 2y ago> This is a project to make F# developer to write blazor easier Now do the same in Visual Studio New Project, language F# or VB, without similar community projects.
- neonsunset 2y agoI doubt that teams which employ F# are affected by default template selection in Visual Studio in any way, shape or form (if they use VS at all) :) And companies which strictly choose only whatever comes out of box are unlikely to use F# anyway. The concept itself is incorrect and, I argue, must not be applied beyond ASP.NET Core and EF Core. There are no "first-party" frameworks in many other languages in either case so it is an unfair and flawed argument in the context of .NET.
- pjmlp 2y agoNot unfair at all, and a clear shift of goalposts from how .NET was sold in 2001, and has been for almost 15 years, until management decided only C# gets invited for the new party. Do you want a refresh from Visual Studio.NET and further releases until this stop being a thing?