by doing (await ml, await al), if al threw before ml was fully awaited, it would cause an unhandled exception (because different thread so the try catch in MainWindowViewModel wouldn't catch it). This would lead to scarab just showing blank screen with no error or anything. Although it's less efficient, its better to handle errors properly
If you want to reproduce the bug just turn off wifi and open scarab again and again until it happens. With being offline it happened around 25% of the time for me
by doing (await ml, await al), if al threw before ml was fully awaited, it would cause an unhandled exception (because different thread so the try catch in MainWindowViewModel wouldn't catch it). This would lead to scarab just showing blank screen with no error or anything. Although it's less efficient, its better to handle errors properly