I did this too, I have pi that downloads and combined a bunch of rss feeds every 30min (cron) and downloads the vids, I browse them with Thunderbird on my desktop, I inject a special link to the mp4 on my pi. So I can just watch vids at 192.168.1.106/videos/X.mp4 using the Firefox mp4 player.

Did it in ~300 lines of node.js, was trying to learn how to use JS for server stuff, seemed like a good idea at the time. It still works 5 years later, but it stands as a reminder to me to never use async/await.

Not using async/await is worse: you get sucked into then/catch, or worse, callback hell or shudder streams, which are known to be full of footguns and typically only approximate working correctly.

Of course you can go full sync if your app wouldn’t do anything useful during the time it’s blocked waiting for network or I/O.

> a reminder to me to never use async/await

What issues did you face with async/await?