Current API uses polling mechanism to poll updates, which eats CPU quite heavily.
Of course if you have 1 second polling mechanism like
https://github.com/RuntimeCompiledCPlusPlus/RuntimeCompiledCPlusPlus/wiki
does, then CPU usage cannot be seen, as it does not consume so much CPU as in SimpleDemo, but it consumes CPU still.
Would it be difficult to recode API to use threads instead ?
Also in newest c++ standards I've noticed that new class std::filesystem appeared, which deals with file system path/folders creation / directory / files enumeration - I think it's perfect from standardization perspective. Would like to see file watcher also standardized. Does makes any sense to switch api to lower case and move into std namespace, so it would be easier to integrate later on under the same umbrella ? :-)
Current API uses polling mechanism to poll updates, which eats CPU quite heavily.
Of course if you have 1 second polling mechanism like
https://github.com/RuntimeCompiledCPlusPlus/RuntimeCompiledCPlusPlus/wiki
does, then CPU usage cannot be seen, as it does not consume so much CPU as in SimpleDemo, but it consumes CPU still.
Would it be difficult to recode API to use threads instead ?
Also in newest c++ standards I've noticed that new class std::filesystem appeared, which deals with file system path/folders creation / directory / files enumeration - I think it's perfect from standardization perspective. Would like to see file watcher also standardized. Does makes any sense to switch api to lower case and move into std namespace, so it would be easier to integrate later on under the same umbrella ? :-)