Comparison between libui-node & libui-napi

[parro-it]

I completed the initial implementation of windows, boxes and multiline entry.
I then created a new branch from 0_3_0 branch of libui-node, removed all the stuff except windows, boxes and multiline entry.
Here is a comparison of the two implementation to help decide if the N-API rewrite is worth the effort:

nbind version

binary size: 627Kb
compilation time: 39s
runtime memory consuption of example.js: 21M

N-API version

binary size 56Kb
compilation time: 7s
runtime memory consuption of example.js: 18M

Considering also that N-API greatly simplify publish of prebuilt binaries, and that it offer much control on memory management and type conversion, my opinion is that the conversion it's totally
worth the effort.

[mischnic]

What about compatibility?

[parro-it]

You mean at API level? It's pretty good

You can compare https://github.com/parro-it/libui-node/blob/0_3_0/examples/example-from-napi.js and https://github.com/parro-it/libui-napi/blob/master/example/using-classes/index.js

[mischnic]

Great, but what I really meant is node support for NAPI.

[parro-it]

It works with node >=8

[parro-it]

Are you concerned on getting support for older versions?

[mischnic]

Are you concerned on getting support for older versions?

(Most likely not worth it.)

[mischnic]

It works with node >=8

libui-napi/package.json

Lines 19 to 21 in ee33206

	"engines": {
	"node": ">=10"
	},

Well..

[parro-it]

Fixed!

[parro-it]

Regarding how to organize the development, I'm in doubt if it would be better to move all the stuff
I already did here to a new branch in libui-node, or otherwise keep libui-napi as a separate repo and
use libui-node only for the wrapper classes.
Any thought?

[mischnic]

use libui-node only for the wrapper classes.

What wrapper classes?

[parro-it]

These: https://github.com/parro-it/libui-napi/tree/master/js
The native part now bind libui functions one-by-one, and these classes should provide the same API as previews release.

[mischnic]

Any thought?

Not sure.
Everything being in one place might make development easier.

[mischnic]

What about linux and windows?

Windows doesn't like the _Atomic(bool) syntax.
Linux doesn't know pthread_rwlock_t.

[parro-it]

Everything being in one place might make development easier.

Yes, I agree.