by TIV73 » Fri Aug 25, 2017 3:13 pm
Good evening,
currently, promises are extensively used in MediaMonkey due to the obvious benefits asynchronous workflows provide. A while ago, the chromium engine implemented async functions, which kind of extend the idea of promises. Unfortunately, those functions are currently not available in MediaMonkey since it uses version 53, which predates them.
These keywords can, by a large margin, improve readability for functions that heavily rely on promises. Plus, the chrome remote protocol (used here for example) needs async/await functionality to proper handle asynchronous calls. Right now, getting data from Mediamonkey to an external interface in an asynchronous workflow requires workarounds that are either hit or miss, or sacrifice performance for functionality.
Is there any chance we are going to see an upgrade to a more recent version of the chromium engine in MediaMonkey soon?
Good evening,
currently, promises are extensively used in MediaMonkey due to the obvious benefits asynchronous workflows provide. A while ago, the chromium engine implemented async functions, which kind of extend the idea of promises. Unfortunately, those functions are currently not available in MediaMonkey since it uses version 53, which predates them.
These keywords can, by a large margin, improve readability for functions that heavily rely on promises. Plus, the chrome remote protocol (used here for example) needs async/await functionality to proper handle asynchronous calls. Right now, getting data from Mediamonkey to an external interface in an asynchronous workflow requires workarounds that are either hit or miss, or sacrifice performance for functionality.
Is there any chance we are going to see an upgrade to a more recent version of the chromium engine in MediaMonkey soon?