Live data from Hacker News

Proton Native – React Native for the desktop

proton-native.js.org

121–130 of 295 posts

Re: Proton Native – React Native for the desktop

#121

Earlier quoted context omitted.

What do you mean? Can you provide some links for building OSX apps with ReactNative? Only iOS/Android are listed as targets on the documentation website (under getting started) .

https://github.com/Microsoft/react-native-windows https://github.com/ptmt/react-native-macos

But aren't those 3rd party react native for desktop implementations, just like Proton Native? Does Proton Native differ in some meaningful way that OP was referring to?

We're in a thread about a React Native for desktop implementation.. saying "React Native is React Native for Desktop" is confusing; hence my question.

Re: Proton Native – React Native for the desktop

#122

Earlier quoted context omitted.

Anything that reduces the number of running chrome instances on my poor little laptop would be nice.

Chrome is like the elephant that comes and sits on my laptop. Would be unusable without the great suspender.

I got a recent Great Suspender update that blew away my settings for the plugin. Did this happen to you too? It made me sad.

Re: Proton Native – React Native for the desktop

#123

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!

Anything that reduces the number of running chrome instances on my poor little laptop would be nice.

I tried out the example "Notepad" app in the git repo and it ran at 70MB. Is that good? I don't have any metrics about how much memory a hello world Electron app uses.

Re: Proton Native – React Native for the desktop

#124
post #22
post #4

> It is not only shorter, it is also easier to read and to edit, and can easily utilize the power of the state. Easier to read and edit is obviously subjective, but shorter is not and that front page is just straight up lying. The Qt example is most definitely shorter. What am I missing?

Hey. I'm the author. It's hard to find a simple example that everyone understands but can show capabilities. If you're used to Qt then you're going to like Qt better, but I mainly developed this for people who want to use React. You are obviously free to use whatever you want. But if you have any suggestions let me know!

I guess just drop the comparison with Qt or other similar things. Just highlight that you can build native applications using React syntax. This alone is a good argument, no point on comparing, really. Only if you want to compare performance, etc.

Re: Proton Native – React Native for the desktop

#126
post #38

Earlier quoted context omitted.

These are interesting points (although I don't quite follow some of your explanations). I've been trying to learn more about the history of GUI development, so I appreciate hearing about how it's been done. Here's an interesting discussion of Delphi (2013): https://news.ycombinator.com/item?id=7613543

Sure - it was quick! Here's a short overview of how Delphi's UI design works. First, you have a visual form designer: drop a button, resize it, edit the caption, etc. All objects like buttons, edit boxes etc are classes with properties. They live on a form, another class. The key is object streaming . The form has instance variables: a private MyButton : TButton, for example, where TButton is the type. This list of f…

The downside was, that UI design was visual, Delphi used absolute positioned layout and everyone was using pixels (despite VCL supporting ptpx).

Allaire Homesite (one of the early HTML editors), written in Deplhi, was one of the first apps that openly ignored the pt sizing and was broken on computers with Large Fonts setting enabled. After that, everyone started ignoring the DPI, and that is what got us into today's HiDPI mess.

Yes, I was pissed of at the time. I was using Large fonts. During a short time, that option became unusable, because nobody bothered with DPI, when drag and drop UI design is so easy.

Re: Proton Native – React Native for the desktop

#127

Earlier quoted context omitted.

Anything that reduces the number of running chrome instances on my poor little laptop would be nice.

I tried out the example "Notepad" app in the git repo and it ran at 70MB. Is that good? I don't have any metrics about how much memory a hello world Electron app uses.

Another thread quoted 300MB baseline

Re: Proton Native – React Native for the desktop

#128

Earlier quoted context omitted.

I'd love to see electron "suddenly" start reducing memory footprint as soon as a competitor starts gaining market share

Actually, earlier today Electron 2.0.0 dropped and includes an `affinity` option, which throws everything under one process. Supposed to help with memory/resource usage.

Wow, nice! Didn't think there was much room to improve given the dependency on Chrome.

Re: Proton Native – React Native for the desktop

#129

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!

Isn't it running on Node?

[deleted]

Re: Proton Native – React Native for the desktop

#130

Earlier quoted context omitted.

Anything that reduces the number of running chrome instances on my poor little laptop would be nice.

I tried out the example "Notepad" app in the git repo and it ran at 70MB. Is that good? I don't have any metrics about how much memory a hello world Electron app uses.

Well, that seems a bit too much. For comparison, take a look at this example electron app that I wrote to basically check if you're online using IPC.

https://i.imgur.com/g94LOvE.png

It uses around 35MB.

Post reply on HN