{"action":"created","issue":{"url":"https://api.github.com/repos/Microsoft/visualfsharp/issues/803","labels_url":"https://api.github.com/repos/Microsoft/visualfsharp/issues/803/labels{/name}","comments_url":"https://api.github.com/repos/Microsoft/visualfsharp/issues/803/comments","events_url":"https://api.github.com/repos/Microsoft/visualfsharp/issues/803/events","html_url":"https://github.com/Microsoft/visualfsharp/issues/803","id":122648258,"number":803,"title":"How to drive F# Adoption Part 2","user":{"login":"KevinRansom","id":5175830,"avatar_url":"https://avatars.githubusercontent.com/u/5175830?v=3","gravatar_id":"","url":"https://api.github.com/users/KevinRansom","html_url":"https://github.com/KevinRansom","followers_url":"https://api.github.com/users/KevinRansom/followers","following_url":"https://api.github.com/users/KevinRansom/following{/other_user}","gists_url":"https://api.github.com/users/KevinRansom/gists{/gist_id}","starred_url":"https://api.github.com/users/KevinRansom/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/KevinRansom/subscriptions","organizations_url":"https://api.github.com/users/KevinRansom/orgs","repos_url":"https://api.github.com/users/KevinRansom/repos","events_url":"https://api.github.com/users/KevinRansom/events{/privacy}","received_events_url":"https://api.github.com/users/KevinRansom/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":13,"created_at":"2015-12-17T02:37:11Z","updated_at":"2015-12-17T08:56:28Z","closed_at":null,"body":">F# is great programming language and yet it is under utilized. I would like to understand what you the enthusiast F# developer believes are the top four things we can do to drive adoption: As a developer I believe they are features, if someone has already suggested your top thing, repeat it in your list anyway.\r\n Please keep discussion to a minimum for this exercise. We can discus the results elsewhere, later. I just want to get a feel for everyone people thinks.\r\n\r\nIn \"How to drive adoption part 1\"  https://github.com/Microsoft/visualfsharp/issues/798\r\n\r\nWe collected some data here is the summary.  Please review the summary and let me know if I missed something you intended to be added.\r\n\r\nPlease try to rank the 10 items in the order you think will be the most effective in converting curious F# investigators into consistent developers.\r\nPlease try to rank the 10 items in the order you think are the ones the community can best deal with.\r\nWhen ranking, if you feel some items are not significant just leave them out of the ranking.\r\n\r\n__I know this seems school maam'ish of me, I apologise, but in order to get to actionable items, we need to figure out what we need to do.  Your input is valued, but digressions limit the value of this exercise.__\r\n\r\nTo summarize:\r\n1. More Microsoft Evangelism / Requiring other product groups to make their stuff F# ready\r\n2. Better Tooling (E.g Make Power Tools available for VS, Folders in the project system ...)\r\n3. CoreCLR support\r\n4. Revive FSI ...\r\n5. ASP.NET v.next support (Not sure if this is coreclr or tooling or both)\r\n6. Language Improvements (Various suggestions)\r\n7. Compiler Performance.\r\n8. Better dependency management.\r\n9.. UWA support for creating truly universal apps .... for Windows.8. Improved F# => C# interop ( enables F# libraries to be better consumed from C#)\r\n10. Steffen said we should logically add curly braces .... (I'm guessing that was irony or sarcasm :-) )\r\n\r\n"},"comment":{"url":"https://api.github.com/repos/Microsoft/visualfsharp/issues/comments/165387352","html_url":"https://github.com/Microsoft/visualfsharp/issues/803#issuecomment-165387352","issue_url":"https://api.github.com/repos/Microsoft/visualfsharp/issues/803","id":165387352,"user":{"login":"enricosada","id":147243,"avatar_url":"https://avatars.githubusercontent.com/u/147243?v=3","gravatar_id":"","url":"https://api.github.com/users/enricosada","html_url":"https://github.com/enricosada","followers_url":"https://api.github.com/users/enricosada/followers","following_url":"https://api.github.com/users/enricosada/following{/other_user}","gists_url":"https://api.github.com/users/enricosada/gists{/gist_id}","starred_url":"https://api.github.com/users/enricosada/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/enricosada/subscriptions","organizations_url":"https://api.github.com/users/enricosada/orgs","repos_url":"https://api.github.com/users/enricosada/repos","events_url":"https://api.github.com/users/enricosada/events{/privacy}","received_events_url":"https://api.github.com/users/enricosada/received_events","type":"User","site_admin":false},"created_at":"2015-12-17T08:56:28Z","updated_at":"2015-12-17T08:56:28Z","body":"i think these points are a nice but really difficult to execute.\r\nIt's the same list ( + coreclr/azure ) as usual\r\nIt's difficult to fix problems if we as community and ms duplicate the work.\r\n\r\n- ms (as visualfsharp team) doesnt have bandwidth to implement all features ( it's not roslyn team, @KevinRansom and others are doing lots of work for 2-3 people ).\r\n- community can contribute, but up to a point. Now we can contribute, but bar is low and slow. and it's fragmented.\r\n\r\nThis repo is really entangled ( ide, compiler, compiler service, fsi, fsharp core library ), it's not needed to have like that. Roslyn is not in the same repo as corefx for a reason.\r\n\r\nDuplicated effort:\r\n\r\n- vs ide: visualfsharp vs fsharp power tools\r\n- download and run: visualfsharp vs openfsharp\r\n- compiler: visualfsharp vs openfsharp vs compiler service\r\n- sync between repos ( 3 repos atm )\r\n\r\nI think it's better to try to develop *with community* instead of accept contribution ( patch, features ) only.\r\nIf that mean split responsability of repositories to have a faster loop ( that mean **quality and features** ) so be it.\r\nLeave ide code code in visualfsharp, but move compiler code in openfsharp repo **only**. Develop there the compiler service if possible.\r\nMove fsharp core to openfsharp, split core library as a simple nuget, so easier to develop, test and publish ( like FSharp.Core nuget now )\r\nHave you visualfsharp team contribute to openfsharp compiler code and compiler service. Use compiler service instead of a duplicated version.\r\nSplit project system vs language service in visualfsharp, try to merge language service with VFPT and develop there.\r\n\r\nMy dream list :smile: "}}