News for hackers. Stuff that matters.

A comment on Proton Native – React Native for the desktop.

Re:Proton Native – React Native for the desktop by memonkey on Wednesday May 02, 2018 @01:53PM (#16979489)
This is super cool. Are there any demonstrations comparing performance between electron and your app?
[ Parent | on HN ]
Re:Proton Native – React Native for the desktop by caspervonb on Wednesday May 02, 2018 @02:19PM (#16979745)
It seems to runs on "UI" from andlabs, which is a fairly lightweight C wrapper around the the Windows, Cocoa and Gtk API's.

Sidenote as for why a UI library would wrap another UI wrapping library, Gtk is what is considered "native" on Gnome based distros.

So weight-wise, it's basically comes at the cost of native node module which is not bad compared to Electron's crazy IPC bridge back and forth communication nonsense.

[ Parent | on HN ]
Re:Proton Native – React Native for the desktop by zengid on Wednesday May 02, 2018 @02:45PM (#16979979)
>So weight-wise, it's basically comes at the cost of native node module

And now with NAPI [1] it should be easier than ever to make node modules!

[1] https://nodejs.org/api/n-api.html#n_api_n_api

[ Parent | on HN ]
Re:Proton Native – React Native for the desktop by parro-it on Thursday May 03, 2018 @03:00AM (#16983892)
Some days ago I started a N-API version of the bindings: https://github.com/parro-it/libui-napi

Is still really incomplete compared to libui-node, but just in case someone wants to help

[ Parent | on HN ]
Re:Proton Native – React Native for the desktop by zengid on Thursday May 03, 2018 @08:30PM (#16991225)
Is it a pretty simple re-write or something that requires a lot of c wizardry?
[ Parent | on HN ]
Re:Proton Native – React Native for the desktop by parro-it on Friday May 04, 2018 @12:45PM (#16995984)
Not a simple rewrite, but neither a task that require a C wizard... The current version of libui-node implements C++ classes that wraps libui C function. They are exposed directly to JS. This experiment implements N-API C functions that wraps libui C function. Then, a set of JS classes wrap them, offering the same public API as libui-node.

Currently, I implemented windows, boxes, and multiline entry. I have to compare this experiment with the curent implementation in terms of erformance, memory consuption etc. before to decide to continue with N-API or not.

[ Parent | on HN ]
Re:Proton Native – React Native for the desktop by parro-it on Friday May 04, 2018 @01:48PM (#16996584)
FYI, I just wrote the comparison I was speaking above: https://github.com/parro-it/libui-napi/issues/11
[ Parent | on HN ]
Re:Proton Native – React Native for the desktop by zengid on Saturday May 05, 2018 @12:48AM (#17000376)
Pretty impressive results!
[ Parent | on HN ]
Re:Proton Native – React Native for the desktop by parro-it on Tuesday May 08, 2018 @04:04PM (#17024394)
Yes, N-API seems to be superior. And it's a particular good fit because libui itself has a C API
[ Parent | on HN ]
Re:Proton Native – React Native for the desktop by kusti8 on Wednesday May 02, 2018 @02:02PM (#16979585)
Currently no. That's one thing that I want to test sometime, but right now I'm busy improving it.
[ Parent | on HN ]
Re:Proton Native – React Native for the desktop by wilonth on Wednesday May 02, 2018 @02:47PM (#16979990)
I dont think that'd be very useful. Proton is pretty much native C with just a JS runtime on top, it might even be faster than Qt. So a benchmark against Qt maybe?
[ Parent | on HN ]
Re:Proton Native – React Native for the desktop by jcelerier on Wednesday May 02, 2018 @05:59PM (#16981519)
Qt's event loop is much faster than node's though ; see for instance benchmarks of web servers using either : look at the scores of Cutelyst vs the score of Node servers here : https://www.techempower.com/benchmarks/#section=data-r15&hw=...
[ Parent | on HN ]