Ok, I could read the "experimental local file" post (thanks for the link —), this is however limited compared to NW.js (by the way, I didn't know that desktop maintenance was so heavy but I am now aware of that). It is also indicated (just 10 days ago) that desktop builds would no longer have support "in the long term", so it seems a bit early to start removing download links as early as 2020, isn't it?
umarfarooq: Did you activate the different hardware acceleration options in Chrome settings and flags? This changed the game on my side, I had completely forgotten to have disabled them to solve crashes on another webapp several months ago (my fault, sorry). Now I'm much closer to desktop performance even if it's slightly slower (no other tab or Chrome extension are used 
piranha305, but it's good, it works pretty well, even very well - out of this greedy 50-70% memory usage difference).
oosyrag, —
For files in Chrome, NW.js will indeed be missing a lot, despite the beginning of a solution in the other post while awaiting clear improvements, this is IMHO a cumbersome process.
Regarding other solutions: Changing CORS settings in Chrome does not reassure me at all for security, especially if I have to navigate when Construct is open (ok, I still don't like the idea of sharing my browser or to use a browser when working with such a powerful application, but I have to accept it or I will end up sinking in utter dismay and despair ^_^).
When I develop, design or test, and without wanting to repeat myself, I like to automatically load files, images, animations, data, tilemaps, audio, etc. and all changes on the fly, without having to import everything by hand each time, which makes me save more than considerable time and comfort (while also avoiding tendonitis and other holy "special" moments).
As an alternative and after a few tests, I load these asset sources via a local web server (WampServer), it works well even if this adds additional constraints in the work organization. Fortunately, I don't need to install an SSL certificate for the moment and the basic HTTP protocol seems to be enough (sweat).