I have a giant FLAC collection and I sometimes wish I could use these local players because I used Winamp/XMMS/quod libet back in the day, but I feel like I just can’t give up consistent access from outside the house.

I ran Tauon for a while (and have run a few of the others over the years) but I always end up back at my Airsonic setup. Works in any browser, works in a few different Android apps (Subsonic compatible), less of a pain than mpd.

Maybe it’d be different if I was still sitting in front of my computer virtually all the time, but nowadays phone to Bluetooth speaker/car/Chromecast is like 90% of my listening.

Basically, the executing thread might get interrupted in a window of code where the interrupt flags are wrong. Not looking at the specifics, but this could lead to various things from mostly harmless (e.g. potentially holding a lock for many times longer than expected but eventually releasing it) to program crashing (e.g. if taking an interrupt while handling the fault leaves the data structures in an inconsistent state).

This is likely the first one, since it was missed for so long in a very well exercised piece of code.

I wouldn’t do a mailing list these days, but as someone who spent the early part of my career interacting with devs that preferred this method, it’s actually pretty ergonomic by a 2005 standard. A message thread aware, text based email client that can turn messages into patches in a keystroke makes it actually pretty comparable to modern code review…

I think it’s hard for younger devs to get this because they’re used to email being stuck in a crappy, unthreaded browser interface or Outlook etc. (which are terrible for mailing lists) and most collaboration taking place in code review and chat platforms like Teams/Slack but for decades before these were feasible, email was the way…