{"action":"closed","issue":{"url":"https://api.github.com/repos/Microsoft/cppwinrt/issues/277","repository_url":"https://api.github.com/repos/Microsoft/cppwinrt","labels_url":"https://api.github.com/repos/Microsoft/cppwinrt/issues/277/labels{/name}","comments_url":"https://api.github.com/repos/Microsoft/cppwinrt/issues/277/comments","events_url":"https://api.github.com/repos/Microsoft/cppwinrt/issues/277/events","html_url":"https://github.com/Microsoft/cppwinrt/issues/277","id":274984937,"number":277,"title":"Windows Runtime needs much more attention","user":{"login":"Alovchin91","id":8490695,"avatar_url":"https://avatars1.githubusercontent.com/u/8490695?v=4","gravatar_id":"","url":"https://api.github.com/users/Alovchin91","html_url":"https://github.com/Alovchin91","followers_url":"https://api.github.com/users/Alovchin91/followers","following_url":"https://api.github.com/users/Alovchin91/following{/other_user}","gists_url":"https://api.github.com/users/Alovchin91/gists{/gist_id}","starred_url":"https://api.github.com/users/Alovchin91/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/Alovchin91/subscriptions","organizations_url":"https://api.github.com/users/Alovchin91/orgs","repos_url":"https://api.github.com/users/Alovchin91/repos","events_url":"https://api.github.com/users/Alovchin91/events{/privacy}","received_events_url":"https://api.github.com/users/Alovchin91/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":7,"created_at":"2017-11-17T20:19:20Z","updated_at":"2017-11-21T19:17:13Z","closed_at":"2017-11-21T19:17:13Z","author_association":"NONE","body":"Since many people (me among them) believe this project is the future of Windows Runtime, I think this is the best place for this suggestion.\r\n\r\nWindows Runtime is a much better COM, which means this could and _should_ be **the** technology for the Modern Windows API. But for now, it doesn't get enough attention.\r\n\r\nWhat I'm talking about is that, few years into Windows 10 and almost 6 years into Windows Runtime, UWP is a failed experiment. And Windows Runtime **needs** to break through the boundaries of this experiment.\r\n\r\nSince it's a much better COM, it should be fully available for traditional Win32 apps to accomplish their tasks within the Modern Windows OS. This means:\r\n\r\n* Extending available WinRT APIs to the state where they can supersede the traditional Win32 API\r\n* Allowing Win32 apps to consume custom WinRT components. This is especially useful in terms of .NET apps that need interop with native code. This is a much better registration-free COM, this _should_ be **the** technology for this kind of tasks!\r\n* Since WinJS is no longer developed, and Fluent design is not supported for WinJS apps, and we hear less and less about HTML/JavaScript UWP apps, Windows Runtime vNext should consider moving away from JS support. This would make those custom WinRT components much more ABI friendly: you would be able to write non-sealed classes (like current XAML ones), jagged arrays, custom exceptions, etc. etc.\r\n\r\nLike many people following this project, I believe Windows Runtime is the future of Windows API. But for now, it is stuck on failed UWP experiment. It needs to break through these chains to shine."}}
{"actor":{"display_login":"kennykerr"}}