{"action":"created","issue":{"url":"https://api.github.com/repos/dotnetfringe/dotnetfringe.github.io/issues/73","repository_url":"https://api.github.com/repos/dotnetfringe/dotnetfringe.github.io","labels_url":"https://api.github.com/repos/dotnetfringe/dotnetfringe.github.io/issues/73/labels{/name}","comments_url":"https://api.github.com/repos/dotnetfringe/dotnetfringe.github.io/issues/73/comments","events_url":"https://api.github.com/repos/dotnetfringe/dotnetfringe.github.io/issues/73/events","html_url":"https://github.com/dotnetfringe/dotnetfringe.github.io/issues/73","id":142405157,"number":73,"title":"What is the burning question for the future of .NET / Core CLR / Mono today?","user":{"login":"Adron","id":278870,"avatar_url":"https://avatars.githubusercontent.com/u/278870?v=3","gravatar_id":"","url":"https://api.github.com/users/Adron","html_url":"https://github.com/Adron","followers_url":"https://api.github.com/users/Adron/followers","following_url":"https://api.github.com/users/Adron/following{/other_user}","gists_url":"https://api.github.com/users/Adron/gists{/gist_id}","starred_url":"https://api.github.com/users/Adron/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/Adron/subscriptions","organizations_url":"https://api.github.com/users/Adron/orgs","repos_url":"https://api.github.com/users/Adron/repos","events_url":"https://api.github.com/users/Adron/events{/privacy}","received_events_url":"https://api.github.com/users/Adron/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":8,"created_at":"2016-03-21T16:45:29Z","updated_at":"2016-03-22T17:45:32Z","closed_at":null,"body":"What do you see as the burning issues and questions of the community today?\r\n\r\n- Will Core CLR work? When will it be usable in production?\r\n- What's the lifespan of Mono, since it's still the only real viable .NET x-plat solution?\r\n- How will Xamarin fit into the fold at Microsoft?\r\n  - What new OSS directions will MS & Xamarin's team bring to the community?\r\n  - What's the future hold for mobile as MS pushes toward a more iOS & Android future?\r\n- What's the future hold for distributed systems @ Microsoft? Will Orleans or Akka .NET bring us a viable disitributed systems story finally for the .NET Community (or would you argue it already has?)\r\n- What does the future hold for F#? Microsoft seems to putter along but the F# Community has delivered some of the most modern and advanced capabilities for the .NET stack with F#, what would it take to get more of the community involved with the language?\r\n- Java has an absurd level of libraries, in many cases far outpacing the .NET stack and with Core CLR, the entire list of libraries needs rewritten. How do you see the community filling that gap? How are you contributing to bringing the Core CLR to the forefront and into the future?\r\n- How will Microservices shape the future of Nancy, ASPNET, and related frameworks and tools? Will it relapse into a more heavy handed SOA style architecture?\r\n\r\nWhat other things weigh on your mind about the future of the .NET Stack? Will C# continue it's dominance in the stack? Will new languages crop up to fill the weak spots of C#? Will more learn F# to bring its strengh into more focus and push the stack forward as Scala has been used in the Java stack? Will things continue to be simplified following KISS to make the ASPNET stack more and more like how Node.js has come to form the server side JavaScript stack?\r\n\r\nLet's talk, throw in a comment or three!  :+1: "},"comment":{"url":"https://api.github.com/repos/dotnetfringe/dotnetfringe.github.io/issues/comments/199931508","html_url":"https://github.com/dotnetfringe/dotnetfringe.github.io/issues/73#issuecomment-199931508","issue_url":"https://api.github.com/repos/dotnetfringe/dotnetfringe.github.io/issues/73","id":199931508,"user":{"login":"iancooper","id":45537,"avatar_url":"https://avatars.githubusercontent.com/u/45537?v=3","gravatar_id":"","url":"https://api.github.com/users/iancooper","html_url":"https://github.com/iancooper","followers_url":"https://api.github.com/users/iancooper/followers","following_url":"https://api.github.com/users/iancooper/following{/other_user}","gists_url":"https://api.github.com/users/iancooper/gists{/gist_id}","starred_url":"https://api.github.com/users/iancooper/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/iancooper/subscriptions","organizations_url":"https://api.github.com/users/iancooper/orgs","repos_url":"https://api.github.com/users/iancooper/repos","events_url":"https://api.github.com/users/iancooper/events{/privacy}","received_events_url":"https://api.github.com/users/iancooper/received_events","type":"User","site_admin":false},"created_at":"2016-03-22T17:45:32Z","updated_at":"2016-03-22T17:45:32Z","body":"\r\n-  Will Core CLR work? When will it be usable in production?\r\n\r\n> CoreCLR will work, and probably be production ready from end of 2016, though 'bet-the-farm' would be mid-2017. The biggest CoreCLR problem remains the clarity of branding message about how to built C# solutions 'tomorrow'. MS may need to shift emphasis to clarify there is a new clean platform that you can transfer your skills too, but would be a migration effort for an application. It also needs to clarify between CLR and Native which are both targets. I would suggest a new 'brand' instead of .NET for the new CLR, and a clearer message around building for different targets. UWP is still too confusig considering the point of a reboot should be to 'simplify' not obfusticate. \r\n\r\n-     What's the lifespan of Mono, since it's still the only real viable .NET x-plat solution?\r\n\r\n>I would expect to see increasing convergance of the Mono and CoreCLR codebases, with pull and push in both directions, but timescales for one and one only would feel more like 2019 than imminent.\r\n\r\n-     How will Xamarin fit into the fold at Microsoft?\r\n\r\n> I would guess the toolchain for x-platform development\r\n\r\n-         What new OSS directions will MS & Xamarin's team bring to the community?\r\n\r\n>I think it's less about new as delivering a framework that takes us from the app in small data center world of .NET to apps in IAAS or PAAS of 'post.NET'. Small runtimes, progressive download, faster update cycles, leaner base class libraries. The competition is node.js etc.\r\n\r\n-         What's the future hold for mobile as MS pushes toward a more iOS & Android future?\r\n\r\n>The UI is shallow in a world where most of the functionality lives on the server, so the question is how much value x-platform gives when you probably need to write device specific UI code. I'd expect changing paradigms of development, a re-emergence of conversations about thin client to be more telling than x-platform over time. What interests me here is that there is a lot of knowledge locked in the .NET community from being the key desktop development toolchain on how to build 'smart' clients that is transferrable to mobile. I would be interested to see opportunities for MS to leverage that before it vanishes.\r\n\r\n-     What's the future hold for distributed systems @ Microsoft? Will Orleans or Akka .NET bring us a viable disitributed systems story finally for the .NET Community (or would you argue it already has?)\r\n\r\n>Akka is a greatl products although there are other 'distributed' platforms than the Actor model i.e. broker (Brighter, MassTransit, NServiceBus) that may be an easier transition, or just using HTTP self-hosted services (though that raises issues of availability if handled naively). Orleans and MS Fabric offerings are platform dependent and so may not get traction in the wider space.\r\n\r\n-     What does the future hold for F#? Microsoft seems to putter along but the F# Community has delivered some of the most modern and advanced capabilities for the .NET stack with F#, what would it take to get more of the community involved with the language?\r\n\r\n>The key problem for F# is that C# is good enough, so the pressure to move is low for most developers and the higher salaries commanded by F# developers can be a disincentive outside of finance as CTOs worry how to resource teams. Crossing the chasm really needs either a 'killer framework' (in the same way that Rails was a 'killer framework') that everyone wants to use which drives adoption, or greater prevalance of success stories built on F# like Jet.com.\r\n\r\n-     Java has an absurd level of libraries, in many cases far outpacing the .NET stack and with Core CLR, the entire list of libraries needs rewritten. How do you see the community filling that gap? How are you contributing to bringing the Core CLR to the forefront and into the future?\r\n\r\n>With a cleaner space the opportunity is actually to clean the slate. the opportunity to build new frameworks can create interest in a platform as it creates chances for developers to grab mindshare. We will be supporting CoreCLR with Brighter (although we have a dependency on a CoreCLR RabbitMQ client for folks using that Broker). As a newer library we would hoppe that CoreCLR support gave us a chance to become better known.\r\n\r\n-     How will Microservices shape the future of Nancy, ASPNET, and related frameworks and tools? Will it relapse into a more heavy handed SOA style architecture?\r\n\r\n>Lots of folks will build microservices using HTTP over Brokers so Nancy and ASP.NET Core have a role to play. I don't think that the ESB issue is quite as prevalent in .NET where smart endpoints and dumb pipes was often the rule. Most tooling was of the lightweight broker variety, outside of the BizTalk hell that some enterprises entered. So I think the reflexes of many .NET devs are more attuned to this world. I think a bigger danger is the lack of practitioners experienced at distributed systems and significant ramp up for the community to understand the trade-offs.\r\n\r\n\r\n"}}