In case you've missed it on Twitter - please vote / give feedback / tell me I'm an idiot:
In case you've missed it on Twitter - please vote / give feedback / tell me I'm an idiot:
The fact that Rider is using FCS for #fsharp support means that we shouldn't expect much better quality and more features than what exists in currently existing tooling (Ionide / XS). Tho, it will be probably more stable.
Actually I expect the support to be pretty minimal - they don't really want to invest into F# ecosystem, but just support mix language solutions. Open sourcing it is also interesting - someone is hoping that Community will build more advanced support, I guess
So ... this NuGet announcements about verified users etc....
For me, it looks like just another way to control ecosystem - OSS is fine as long as you use packages of people we've blessed and accepted. That's not how mature OSS ecosystem should work.
Also, I don't really understand what's the problem of NuGet team - there are so many teams inside of MSFT understanding OSS and community. And NuGet team have ... weird problems with community.
@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.