...The key point is as a small company, we don't have the resources to maintain all those libraries ourselves ...
Alright thanks for sharing your view on native engines and their possible risks (again). I think the sentence on top pretty much sums it up. Don't get me wrong I understood that going native also means dealing with buggy 3rd parties, drivers etc. but you could find problems like that on both ends.
I guess in the end it all comes down to the things we've experienced, I personally didn't experience that many issues while developing software with a native base. I guess you've got some pretty bad experiences with C1, that make you think the way you think about native engines right now.
All that's left for me to say is, if you decide to go on with a web based engine please maintain the base plugins.
Currently you're investing all of your time into C3's development and I get that's why you might not be able to deliver the support we expect to get.
However once C3 is out I'm hoping that you're going to get back to those broken/unfinished plugins and provide the support that the users of those plugins need.
I don't feel the need to give you examples on this regard but you should know best which ones currently really need some attention.
Just jumping in to say that, at least back in the nwjs 13.0 days, you could get nwjs builds to run on XP by dropping dbghelp.dll from the official nwjs package into the build folder. Don't know if that'll still work, I don't have a machine with XP installed around to test, but worth a try?
Even though I have done some "hacky" workarounds in the past with certain types of software, I don't really want to do that with NWjs.
You never know what else you could break by doing a workaround like that and if I would do that, I'd be the one held responsible for the bugs that might appear because of it.
Needless to say, it's good to know that it is possible to do that. However while issues with drivers will get fixed eventually, WinXP (in private use) will completely die out one day.