{"action":"opened","issue":{"url":"https://api.github.com/repos/aspnet/Blazor/issues/286","repository_url":"https://api.github.com/repos/aspnet/Blazor","labels_url":"https://api.github.com/repos/aspnet/Blazor/issues/286/labels{/name}","comments_url":"https://api.github.com/repos/aspnet/Blazor/issues/286/comments","events_url":"https://api.github.com/repos/aspnet/Blazor/issues/286/events","html_url":"https://github.com/aspnet/Blazor/issues/286","id":306158171,"number":286,"title":"Using CoreRT instead of Mono?","user":{"login":"petroemil","id":13720703,"avatar_url":"https://avatars3.githubusercontent.com/u/13720703?v=4","gravatar_id":"","url":"https://api.github.com/users/petroemil","html_url":"https://github.com/petroemil","followers_url":"https://api.github.com/users/petroemil/followers","following_url":"https://api.github.com/users/petroemil/following{/other_user}","gists_url":"https://api.github.com/users/petroemil/gists{/gist_id}","starred_url":"https://api.github.com/users/petroemil/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/petroemil/subscriptions","organizations_url":"https://api.github.com/users/petroemil/orgs","repos_url":"https://api.github.com/users/petroemil/repos","events_url":"https://api.github.com/users/petroemil/events{/privacy}","received_events_url":"https://api.github.com/users/petroemil/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2018-03-17T13:52:31Z","updated_at":"2018-03-17T13:52:31Z","closed_at":null,"author_association":"NONE","body":"While I understand that you want to showcase a semi-working prototype as soon as possible, I believe this project (ASP.NET Core Razor running in a browser, compiled to WebAssembly) should rather push towards achieving this with the official .NET Core toolchain.\r\n\r\nSo this is where my question comes:\r\nWhy are you not using (and improving) [CoreRT](https://github.com/dotnet/corert)'s WebAssembly target instead of Mono? This project would be an excellent motivation for everyone inside and outside of Microsoft to actually build all the parts necessary to make .NET Core in the browser happen.\r\n\r\nFor all of this to become a reality (and a real product) we need\r\n - proper compiler support for .NET Core with WeAssembly support - CoreRT\r\n - a very simple (or low-level) interop library - nothing ASP.NET specific stuff, just the basics, HTML DOM manipulation, subscribing to UI evetns, WebAssembly/JavaScript interop, access to universally available JavaScript APIs (that default functionality that every browser provides out-of-the-box, etc.\r\n - and finally Blazor itself, building on top of all of this, providing an actual (.NET Standard) framework to build web apps\r\n\r\nYes, you would be focusing on delivering an end-to-end solution, but in the meanwhile you would build a foundation that could be used by others to build frameworks more suitable for other scenarios, something like [Fable (for F# developers)](fable.io/), or [Ooui.Wasm (Xamarin.Forms in the browser)](http://praeclarum.org/post/171899388348/oouiwasm-net-in-the-browser)."}}
{"actor":{"display_login":"petroemil"}}