3 ms·
ms still has a long way to go imho. i recently thought about developping my backend on fsharp with dotnet core, on a mac. Well, let me just say that the commit
by bsaul 9y ago
ms still has a long way to go imho.
i recently thought about developping my backend on fsharp with dotnet core, on a mac. Well, let me just say that the commitment of ms to some of their open source projects leave to be desired. documentation is painfully hard to find ( compare to apple or even java main web frameworks, where everything is neatly organized in one place), community is inexistant, the main "getting started" videos on youtube is obsolete ( project file format changed in the meantine)... And the only fsharp plugin for vscode is developped by a third company and requires mono to be installed, for some reason.
Maybe it's just that nobody uses fsharp though. So then i tried to find some general architectural overview of asp.net core, and i didn't even know where to start looking. Ms documentation site is a maze, and you can only find short articles on very detailled subject, but nothing really top down.
Now the reason for all that is of course that the MS users ecosystem is made of consulting companies selling "experts", and training companies selling training. Nobody there has any interest in good, free, online resources.
- deleted 9y ago[deleted]
- oblio 9y agoThey truly have a long way to go, especially concerning awareness. But I feel that things will pick up once they release dotnet core 2.0, which will support dotnet standard 2.0, basically the equivalent to the Java base libraries. Up to now things were still in flux and nobody serious wanted to touch the stuff. Now they've mostly settled down.