5 ms·
I am on the team at Microsoft that helped bring UWP to React Native. If there are questions, feel free to AMA. PS. Many thanks to the Facebook team for buildi
by outside1234 11y ago
I am on the team at Microsoft that helped bring UWP to React Native. If there are questions, feel free to AMA.
PS. Many thanks to the Facebook team for building a great platform in React Native and their critical help in helping us bring Windows to the platform.
- louisphp 11y agoCurrently, it's a fork. Do you have plans to merge it in the main react-native repo? When?
- outside1234 11y agoWe are working on Facebook on the best long term strategy for maintaining UWP support. Our fork is only to add the ReactWindows directory and to otherwise track master in the process.
- Aleman360 11y agoWhy does this generate C# instead of C++?
- the_mitsuhiko 11y agoWhy not? Seems like a reasonable thing to do. Is there a specific reason it should be C++?
- outside1234 11y agoOur 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.
- danmatte 11y agoAs 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.
- KirinDave 11y ago> 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.
- mwcampbell 11y agoI 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.
- KirinDave 11y agoBecause it's 2016 and the notion of pinning to C++ is sort of antiquated. C++ can deliver better performance in some cases, but it also brings about a great deal more risk of security issues involving arbitrary code execution and data corruption. You have to have VERY tight performance requirements to make C++ worth the risk it entails, in my opinion. If the only thing standing between you and a code injection exploit is developer discipline and best practices, then you're in a strictly worse place than managed code.
- deleted 11y ago[deleted]
- drzaiusapelord 11y agoThis is such a concise and informed comment. Why has it been voted down to being barely dim on my screen? These are good arguments. Please reply to stuff like this instead of knee-jerk downvoting.
- V-2 11y agoAgreed. I would actually be curious to read some counterarguments. Alas, noone has offered any
- KirinDave 11y agoI think the community has a prevailing opionion that C# is part of a UWP lock-in and they're concerned about that. I'm sure at least some people think C++ is helpful as a hedge against this.
- luisrudge 11y agodid you fork the cli too? or it's the same CLI for the 3 platforms?
- mullsork 11y agoThis might be far fetched but is there any chance there are plans to enable OSX devs to work with Windows Phone apps? I love my phone, but I can't use anything else than OSX.