Hacker News Reader

Comment by outside1234 | Hacker News Reader

Our belief is that using C# enables many more developers to contribute to the project and build plugins versus using C++0x. That said, this is not a final decision. We are open to making a change here if community overall has a reasoned opinion backed by data for using C++ instead.

View on HN

I do wonder if having two garbage-collected runtimes in the same address space will lead to pathological performance and/or memory usage. But I don't have any solid data on that. Of course, if that is a problem, then it also applies to React Native on Android, but there, it's unavoidable.

As C++ is the native language for the UWP, surely it would map more neatly to the platform?

And the well-known performance and memory advantages, however small, are critical for mobile devices. I don't think Microsoft should commit long-term to C# on mobile just as both Apple and supposedly Google are migrating to Swift as the future of their platforms, for good reason.

My two cents.

> And the well-known performance and memory advantages, however small, are critical for mobile devices.

Windows Phone is many things, and few of those things are good. But in terms of UI responsiveness and overall speed, it puts my android to shame and competes with my iPhone.

And the security story of unmanaged languages is perilously bad. I don't see how people justify it anymore.

Reply on news.ycombinator.com