I found the ability to merge unrelated repositories very useful when collecting various bits of work I did separately and combining it into a single library.
If they're using a LLM to make those decisions, then they're fundamentally unable to provide the reasons for those decisions, because of how LLMs work.
FYI, the very recently released Marathon with the BattleEye rootkit works fine on a maximally trimmed down Windows 10 LTSC, which is what I'm running on my PC (personal console).
My original HomePod has recently regressed in its ability to play songs. It can no longer play one song after another without glitching and repeating a little bit of the previous song. It boggles my mind.
Thank you for writing down this memory. It would fit perfectly on https://folklore.org but unfortunately it seems that the site is no longer accepting new memories.
Threads and locks are fundamentally the wrong abstraction for most scenarios. This is explained in complementary ways in two of the finest technical books ever written, Joe Armstrong's "Programming Erlang" and Simon Marlow's "Parallel and Concurrent Programming in Haskell". I highly recommend both.
Thank you for many fond memories of playing Glider and Pararena.
Whoever is downvoting you for speaking the truth should go stand in a corner. Or try maining BeOS for a while, to experience first-hand what happens when application programmers are forced to use threads and locks.