Earlier quoted context omitted.
Or across multi-platforms with XULRunner from 2006 to 2015.
RIP...
Plus ça change...
Proton Native – React Native for the desktop
111–120 of 295 posts
Re: Proton Native – React Native for the desktop
#112Using 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!
I'd love to see electron "suddenly" start reducing memory footprint as soon as a competitor starts gaining market share
I think it'll be hard because they depend on Chromium for performance, which is practically out of their hands and the project is already very streamlined for what it's doing. But Electron comes with a different set of tools i.e. you have the full browser API and renderer at your disposal.
Re: Proton Native – React Native for the desktop
#113Re: Proton Native – React Native for the desktop
#114Earlier quoted context omitted.
> 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.
> React-Native for WPF already exists.
WPF and Win32 are not the same thing.
Re: Proton Native – React Native for the desktop
#115React Native isn't just for iOS / Android, it also works for macOS and Windows. React Native is React Native for the desktop.
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) .
Re: Proton Native – React Native for the desktop
#116The advantage of this over Qt is the licensing. React is an advantage if you are familiar with it over QML.
One thing to note, the naming convention of props differs from React Native which is a bummer. https://github.com/kusti8/proton-native/issues/9
IIRC the project is a light mapping from libui-node project to React.
Re: Proton Native – React Native for the desktop
#117I 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 seems to be geared for mobile. Proton Native uses bindings with NodeJS (via libui-node, which uses libui), which seems to be (IMO) a much better run-time for the JS part than JavaScriptCore because Node already can handle a huge amount of the OS interop. Also, JIT isn't restricted on desktop the way it is on iOS, so JSCore doesn't have a good reason to be used.
Re: Proton Native – React Native for the desktop
#118Earlier quoted context omitted.
I'm sorry but this seems overstated. There is already two highly competitive navigation libraries: https://github.com/wix/react-native-navigation https://reactnavigation.org Edit: Replaced the word FUD with overstated, to not seem like I'm attacking the author personally.
I looked at the GIF that the first one had on their GitHub page and it doesn't do iOS navigation right at all. I'm not impressed.
You're in pretty much every thread that pops up as a naysayer re: not using UIKit/AppKit/etc. The thing about the link you just pointed out is that it's literally 100% UINavigationController. I've used this in projects and had to work with the native source layer - it's nothing crazy different.
It's iOS-style navigation and transitions through and through.
Re: Proton Native – React Native for the desktop
#119Using 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!
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.
Re: Proton Native – React Native for the desktop
#120Using 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?