I don’t know exactly how the computing performance is, and I’ve never done anything so awesome. But since you said nodejs is not suitable for processing computationally intensive tasks, then I think nw is the same. If you don’t believe me, take a look:
You can try atom/vscode to open 100M files first. They are based on electron, the same as nw. The bad news is that node can only load 1.4G files at a time. The good news is that node modules can be written in C/C++. I don’t know much about the underlying things, so I can only provide this information.
As long as each function is designed to be executed separately, I think there should be no problem. For example, I start a single-process HTTP server locally and then call the system browser to access it. php -S 127.0.0.1:8080 -t /www Server and Client are developed separately. Even if the Server is stuck, the JS in the Client can still run. For encrypted files of about 100MB, the Server and Client must not be stuck. You can consider this at this time The local server side proc_open asynchronously opens a process to perform time-consuming encryption operations. The browser side uses JS to poll at 10-second intervals to learn the task progress. I have not used NW.js, but the idea is similar.
I used PHP7’s mcrypt_blowfish to encrypt and decrypt 10MB data on Ubuntu (i5-3230), which took less than 0.2 seconds and occupied about 40MB of memory.
I don’t know exactly how the computing performance is, and I’ve never done anything so awesome. But since you said
nodejs
is not suitable for processing computationally intensive tasks, then I thinknw
is the same. If you don’t believe me, take a look:You can try atom/vscode to open 100M files first. They are based on electron, the same as nw.
The bad news is that node can only load 1.4G files at a time. The good news is that node modules can be written in C/C++.
I don’t know much about the underlying things, so I can only provide this information.
As long as each function is designed to be executed separately, I think there should be no problem.
For example, I start a single-process HTTP server locally and then call the system browser to access it.
php -S 127.0.0.1:8080 -t /www
Server and Client are developed separately. Even if the Server is stuck, the JS in the Client can still run.
For encrypted files of about 100MB, the Server and Client must not be stuck.
You can consider this at this time The local server side proc_open asynchronously opens a process to perform time-consuming encryption operations.
The browser side uses JS to poll at 10-second intervals to learn the task progress.
I have not used NW.js, but the idea is similar.
I used PHP7’s mcrypt_blowfish to encrypt and decrypt 10MB data on Ubuntu (i5-3230), which took less than 0.2 seconds and occupied about 40MB of memory.