halcwb
commented
4 years ago I absolutely agree. Just the lack of response to your issue is testimony to the problem. A continuous and consistent lack of support and upgrading of a lot of core F# libraries. The same applies to F# tooling. I completely understand that this cannot be thrown at any ones feet and this is no personal attack to library maintainers. This is an observation and could be a major reason why F# hasn't been gaining more popularity. If F# is to survive as a major programming language, this general issue has to be fixed.
At the same time I realize that F# is free of charge, a great language and that I am not able to contribute in any meaningful way (being not even a real programmer).
There are maybe more than 100 libraries (just by the fork count of this repo) that have been built based on the different versions of ProjectScaffold. Which was great, it has been an excellent template. But then came .NET Core and .NET Standard and new project files, FAKE 5 and so-on. Gradually some parts are not working from the old templates: SourceLinks, document generation, FSharpTargetsPath is not detected correctly, etc.
Many of the maintainers are not keen to do these big changes to their libraries, maybe their interest has shifted to other projects. This is too-much of the burden for new people who would like to create some simple PR-fixes, but they cannot get the whole projects to compile anymore.
I think this is dangerous for the whole community and the F# ecosystem. Could we have here in ProjectScaffold a guidance, a WIKI, or something, to help the migration: What is the current best practices of .NET projects and how the different old Scaffold templates (or F# code-blocks) should be migrated to the latest best practices?