Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

React Native on the Universal Windows Platform

blogs.windows.com

Post reply on HN
Print view View original

21–30 of 54 posts

Re: React Native on the Universal Windows Platform

#21

Post by jnbiche »

TheAceOfHearts wrote: post #3

This is a huge game changer. We have OS X support with React Native Desktop [0], so that means only Linux support is missing! I've wondered why we haven't seen a React Native Qt, React Native Gtk+, or React Native Elementary yet. But I guess those communities just aren't very interested in what JS people are up to. [0] https://github.com/ptmt/react-native-desktop

> This is a huge game changer.

Agreed. React Native is turning into what a lot of us were hoping QT/QML would. But QT offers a very poor experience to both users and developers for mobile use, due to both license issues (making users download an additional binary scares most of them off) and to the uncanny valley caused by using non-native widgets. React Native has neither of these problems on mobile.

QT still rules the desktop, but it looks like only React Native offers hope for a true cross-platform GUI framework.

Who would have thought 2 years ago?

Re: React Native on the Universal Windows Platform

#22

Post by KirinDave »

V-2 wrote: post #19
drzaiusapelord wrote: post #17

Earlier quoted context omitted.

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

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

Re: React Native on the Universal Windows Platform

#24

Post by Aleman360 »

V-2 wrote: post #19
drzaiusapelord wrote: post #17

Earlier quoted context omitted.

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

Runtime heap usage.

Re: React Native on the Universal Windows Platform

#26

Post by potomushto »

thibauts wrote: post #10
TheAceOfHearts wrote: post #3

This is a huge game changer. We have OS X support with React Native Desktop [0], so that means only Linux support is missing! I've wondered why we haven't seen a React Native Qt, React Native Gtk+, or React Native Elementary yet. But I guess those communities just aren't very interested in what JS people are up to. [0] https://github.com/ptmt/react-native-desktop

The react-native-desktop author is working on it [1]. [1] https://github.com/ptmt/react-native-desktop/issues/59

Thanks, I'm working on it full-time. If you are an everyday Linux user (especially not Ubuntu) and willing to test and/or answer to some questions please reach me out on unknownliveid@hotmail.com.

Re: React Native on the Universal Windows Platform

#27

Post by whatever_dude »

jgnmello wrote: post #25

Only works with Visual Studio 2015 Enterprise?

It works on anything since it's just for platform support and unrelated to tooling. But on the tooling side, they also have a companion extension for (the free, multi-platform) Visual Studio Code. From the article:

> In addition to this work on the core framework support, Microsoft is also providing open source tools and services to help developers create React Native apps. The React Native extension for Visual Studio Code (https://code.visualstudio.com/) brings an intuitive, productive environment to author and debug React Native apps.

Re: React Native on the Universal Windows Platform

#28

Post by jgnmello »

whatever_dude wrote: post #27
jgnmello wrote: post #25

Only works with Visual Studio 2015 Enterprise?

It works on anything since it's just for platform support and unrelated to tooling. But on the tooling side, they also have a companion extension for (the free, multi-platform) Visual Studio Code. From the article: > In addition to this work on the core framework support, Microsoft is also providing open source tools and services to help developers create React Native apps. The React Native extension for Visual Studi…

So, I can build the repo with community? Because I found this statement "Assuming you have Visual Studio 2015 Enterprise installed" at https://github.com/ReactWindows/react-native/tree/ReactWindo...

Re: React Native on the Universal Windows Platform

#29

Post by shankun »

whatever_dude wrote: post #27
jgnmello wrote: post #25

Only works with Visual Studio 2015 Enterprise?

It works on anything since it's just for platform support and unrelated to tooling. But on the tooling side, they also have a companion extension for (the free, multi-platform) Visual Studio Code. From the article: > In addition to this work on the core framework support, Microsoft is also providing open source tools and services to help developers create React Native apps. The React Native extension for Visual Studi…

In addition to the free extension for VS Code (which is free and open source, and available on Mac, Linux, and Windows), we have a free and open source service called CodePush (https://microsoft.github.io/code-push/) for instantly pushing React Native apps to devices.

Re: React Native on the Universal Windows Platform

#30

Post by KirinDave »

Aleman360 wrote: post #24
V-2 wrote: post #19

Earlier quoted context omitted.

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

Runtime heap usage.

Isn't that a performance concern though? Especially within the context of a react native implementation that environment is already going to push you way above what is achievable with C++.

If we're talking a 5% reduction in the net heap usage for a react native app at the cost of substantially more error prone code, is that really a win? Hell, make it 10%? These apps still readily fit in mobile hardware, and you wouldn't be using react native on a Pi or other more tightly resources embedded system.

Post reply on HN