Krzysztof CieslakLooks like Forge is getting killed by new proj file and NuGet based templates 🤔
I still don't understand why OSS loving #fsharp community still has this tendency of trusting MSFT time and time again. 🙄
7sharp9@k_cieslak Thats why fable is so intriguing and promising, although I thought it was a pity it moved to dontnetcore
@7sharp9 Yeah, Fable is great and potential is high... But I believe that for both Fable and .Net we need better set of tools (scaffolding, project handling, CLI, documentation generation etc.) independent of MSFT.
With all those dependencies on `dotnet` CLI (Fable, templates etc. ) we are again putting all eggs in MSFT basket. And there are 2 problems with that:
1. Most teams in MSFT just doesn't think about #fsharp
2. It's bad for "independent language" marketing.
@k_cieslak As so back to the old fstoml xebex project type thingy again. Sure that would be great, its just a really big job.
Everyone also likes to eat their own flavour icecream too which makes managing this type of thing tricky.
@7sharp9 Well, the problem with fstoml / xebex is deciding what should be aim of the project.
Should it try to replace MsBuild? I don't believe it's possible... probably could be done for small part of core functionality, but replacing MsBuild is something that even MSFT failed at.
Should it be just a layer on top of MsBuild? It's doable (I've investigated this path recently for fstoml) but it has it's own disadvantages.
@k_cieslak Well thats why I didn't go beyond a prototype with xebec.
Building from source projects like cargo was my general aim, as well as removing FSharp.Core hell and target framework hell.