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

Proton Native – React Native for the desktop

proton-native.js.org

Post reply on HN
Print view View original

81–90 of 295 posts

Re: Proton Native – React Native for the desktop

#81

Post by com2kid »

jscholes wrote: post #68
BillinghamJ wrote: post #66

I don't totally understand why this exists to be honest. React Native for desktop is... React Native. It isn't mobile-specific in any way. In fact, it is already possible to make Windows (UWP) and macOS apps with it. If this project was about formalising proper stable support for Windows and macOS within React Native, that would totally make sense. But it seems more like it's trying to be an alternative, under a diff…

> React Native for desktop is... React Native. It isn't mobile-specific in any way. In fact, it is already possible to make Windows (UWP) and macOS apps with it. And what if you want to make a non-UWP app for accessibility or other reasons? Just your standard, straight forward Win32 GUI. Bringing the power of React to that space will still appeal to many.

React-Native for WPF already exists. Same repro as React Native for UWP.

Re: Proton Native – React Native for the desktop

#82

Post by symlinkk »

saagarjha wrote: post #62
a13n wrote: post #53

Earlier quoted context omitted.

You might recognize a few on this list: http://facebook.github.io/react-native/showcase.html

None of those are apps I particularly enjoy using or would want to use.

Facebook? Instagram? Airbnb? We're talking about some of the most popular apps in the world. What exactly is your problem with them?

Re: Proton Native – React Native for the desktop

#83

Post by sydd »

roberttod wrote: post #65

Using Electron, you are rendering each window in Chrome, with some added OS hooks. With Proton, you are using JavaScriptCore with hooks to the native MacOS UIs and APIs. Seems to me that this should use far fewer resources (especially memory) and make it easier to make an App look more 'MacOS'y. Very eager to give it a go!

Yeah, but before we say anything we should look the the performance and memory benchmarks.

Re: Proton Native – React Native for the desktop

#84

Post by rhodysurf »

freedomben wrote: post #13
ilurkedhere wrote: post #3

The example in the getting started section comparing Python Qt isn't very convincing.

I tend to agree. I did years of Qt dev and I would never write something like that, nor have I seen it written like that. It works I suppose, but it's very clearly written to be an easy-to-compare example, not a realist example. To really get an idea of what it would be like to use proton native v. Qt I'd like to see a small but complete project.

Not only that... but maybe its the fact that I use Qt everyday at work (C++) or that I'm not really a front end web dev, but the Python example is easier to grasp on first look.

Re: Proton Native – React Native for the desktop

#86

Post by Benjammer »

symlinkk wrote: post #82
saagarjha wrote: post #62

Earlier quoted context omitted.

None of those are apps I particularly enjoy using or would want to use.

Facebook? Instagram? Airbnb? We're talking about some of the most popular apps in the world. What exactly is your problem with them?

I mean, do you realize that most of the big names on that list have a hybrid solution where they prove concepts, A/B test, and rapidly iterate-on/release new features using React Native, and then they have a native dev team for each platform that goes back and re-implements most of the core features natively?

Re: Proton Native – React Native for the desktop

#88

Post by prophesi »

Benjammer wrote: post #86
symlinkk wrote: post #82

Earlier quoted context omitted.

Facebook? Instagram? Airbnb? We're talking about some of the most popular apps in the world. What exactly is your problem with them?

I mean, do you realize that most of the big names on that list have a hybrid solution where they prove concepts, A/B test, and rapidly iterate-on/release new features using React Native, and then they have a native dev team for each platform that goes back and re-implements most of the core features natively?

Discord is the most impressive one to me. They definitely didn't have those resources when they wrote their iOS app[0].

The Android version is just RxJava, iirc, because of some performance issues they couldn't get around.

[0] https://blog.discordapp.com/using-react-native-one-year-late...

Re: Proton Native – React Native for the desktop

#89

Post by roberttod »

sydd wrote: post #83
roberttod wrote: post #65

Using Electron, you are rendering each window in Chrome, with some added OS hooks. With Proton, you are using JavaScriptCore with hooks to the native MacOS UIs and APIs. Seems to me that this should use far fewer resources (especially memory) and make it easier to make an App look more 'MacOS'y. Very eager to give it a go!

Yeah, but before we say anything we should look the the performance and memory benchmarks.

Absolutely, though I can't think of a good reason why it couldn't be leagues better in performance. I'll post here with some numbers later in the day if no one beats me to it.

Re: Proton Native – React Native for the desktop

#90

Post by matchbok »

RubenSandwich wrote: post #70
matchbok wrote: post #39

Earlier quoted context omitted.

NIBs in macOS/iOS are horrible for development and code review. Using a UI to build UI is slow and clunky. There is no "moving past" it. That's a bad way to develop stuff. We don't do it with HTML, do we? No.

Absolutely, most big mobile development teams I know do not use storyboards or NIBs because they are not easily human reviewable. (A small change will rearrange sections for seemlying no reason.)

Same. I wonder how anyone uses them, honestly.
Post reply on HN