React Native on the Universal Windows Platform • Hacker News Board

Re: React Native on the Universal Windows Platform

#11

Post by outside1234 » Wed, Apr 13, 2016, 6:05 PM UTC

Aleman360 wrote: post #7

outside1234 wrote: post #4

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.

Why does this generate C# instead of C++?

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.

Re: React Native on the Universal Windows Platform

#12

Post by radicalman » Wed, Apr 13, 2016, 6:05 PM UTC

Wish we had riotjs native cuz reactjs sucks like Java swing

Re: React Native on the Universal Windows Platform

#13

Post by Aleman360 » Wed, Apr 13, 2016, 6:06 PM UTC

the_mitsuhiko wrote: post #9

Aleman360 wrote: post #7

Earlier quoted context omitted.

Why does this generate C# instead of C++?

Why not? Seems like a reasonable thing to do. Is there a specific reason it should be C++?

Runtime memory usage and startup perf is better for C++ XAML apps.

Re: React Native on the Universal Windows Platform

#14

Post by KirinDave » Wed, Apr 13, 2016, 6:06 PM UTC

Aleman360 wrote: post #7

outside1234 wrote: post #4

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.

Why does this generate C# instead of C++?

Because 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.

Re: React Native on the Universal Windows Platform

#15

Post by [deleted] » Wed, Apr 13, 2016, 6:09 PM UTC

KirinDave wrote: post #14

Aleman360 wrote: post #7

Earlier quoted context omitted.

Why does this generate C# instead of C++?

Because 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 exploi…

[deleted]

Re: React Native on the Universal Windows Platform

#16

Post by ctangent » Wed, Apr 13, 2016, 6:13 PM UTC

Aleman360 wrote: post #13

the_mitsuhiko wrote: post #9

Earlier quoted context omitted.

Why not? Seems like a reasonable thing to do. Is there a specific reason it should be C++?

Runtime memory usage and startup perf is better for C++ XAML apps.

UWP C# apps are AOT compiled, the startup hit isn't that bad nowadays.

Re: React Native on the Universal Windows Platform

#17

Post by drzaiusapelord » Wed, Apr 13, 2016, 6:15 PM UTC

KirinDave wrote: post #14

Aleman360 wrote: post #7

Earlier quoted context omitted.

Why does this generate C# instead of C++?

Because 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 exploi…

This 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.

Re: React Native on the Universal Windows Platform

#18

Post by mrspeaker » Wed, Apr 13, 2016, 6:21 PM UTC

Wow - great news! We were launching our relatively complex app iOS only, but had some downtime and decided to see how the Android implementation fared: it worked really well (much better than I expected) and hasn't taken much effort to have something that feels really nice.

Now I'm excited to try this project out!

Re: React Native on the Universal Windows Platform

#19

Post by V-2 » Wed, Apr 13, 2016, 6:25 PM UTC

drzaiusapelord wrote: post #17

KirinDave wrote: post #14

Earlier quoted context omitted.

Because 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 exploi…

This 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.

Agreed. I would actually be curious to read some counterarguments. Alas, noone has offered any

Re: React Native on the Universal Windows Platform

#20

Post by KirinDave » Wed, Apr 13, 2016, 6:27 PM UTC

drzaiusapelord wrote: post #17

KirinDave wrote: post #14

Earlier quoted context omitted.

Because 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 exploi…

This 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.

I sit upon my horde of HN karma burning it daily. I knew I'd be downvoted for replying to a language preference quote. Especially given how very charged the C++ community is as they feel increasingly abandoned by Microsoft.

I am just happy one person liked it. :)